GCVE Workshop - 22 September 2026 (14:00-18:00), Luxembourg Before The Vulnopticon Conference - Registration

FKIE_CVE-2026-93123

Vulnerability from fkie_nvd - Published: 2026-09-17 17:18 - Updated: 2026-09-17 17:18
Severity
Summary
In the Linux kernel, the following vulnerability has been resolved: serial: qcom-geni: do not advance stale DMA completions The qcom GENI serial DMA TX completion path advances the transmit fifo by the number of bytes recorded in port->tx_remaining. If uart_flush_buffer() runs after the hardware has completed a DMA transfer but before the DMA completion interrupt has been handled, the serial core resets the transmit fifo while port->tx_remaining still describes the old DMA transfer. A previous fix avoided advancing an empty fifo by checking that the fifo length is at least tx_remaining. That still does not distinguish the old DMA payload from new bytes written after the flush. If userspace writes new data before the stale DMA completion interrupt is handled, the fifo can again contain at least tx_remaining bytes and the stale completion can advance and discard those new bytes. Mark an in-flight DMA transfer stale when the transmit fifo is flushed. The later completion still unprepares the original DMA mapping using the saved length, but it no longer advances the transmit fifo.
References
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/231c84fe7ec40e4a06c398c0591d5b8e823d68e1
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/59faa59c25a0a098fbc86275408d7c8405015702
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/7ea38c49e7178960926657863299face6dc0e1b0
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/c02d030747c46da33faf406dd772ef91100efa27
Impacted products
Vendor Product Version
To clipboard 

{
  "affected": [
    {
      "affectedData": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "drivers/tty/serial/qcom_geni_serial.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "231c84fe7ec40e4a06c398c0591d5b8e823d68e1",
              "status": "affected",
              "version": "2aaa43c7077833301c237684cd7bc9ae5e3dec95",
              "versionType": "git"
            },
            {
              "lessThan": "c02d030747c46da33faf406dd772ef91100efa27",
              "status": "affected",
              "version": "2aaa43c7077833301c237684cd7bc9ae5e3dec95",
              "versionType": "git"
            },
            {
              "lessThan": "59faa59c25a0a098fbc86275408d7c8405015702",
              "status": "affected",
              "version": "2aaa43c7077833301c237684cd7bc9ae5e3dec95",
              "versionType": "git"
            },
            {
              "lessThan": "7ea38c49e7178960926657863299face6dc0e1b0",
              "status": "affected",
              "version": "2aaa43c7077833301c237684cd7bc9ae5e3dec95",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "drivers/tty/serial/qcom_geni_serial.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "6.3"
            },
            {
              "lessThan": "6.3",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.12.*",
              "status": "unaffected",
              "version": "6.12.110",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.18.*",
              "status": "unaffected",
              "version": "6.18.52",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "7.2.*",
              "status": "unaffected",
              "version": "7.2.6",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "7.3-rc1",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
    }
  ],
  "cveTags": [],
  "descriptions": [
    {
      "lang": "en",
      "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nserial: qcom-geni: do not advance stale DMA completions\n\nThe qcom GENI serial DMA TX completion path advances the transmit fifo by\nthe number of bytes recorded in port-\u003etx_remaining.\n\nIf uart_flush_buffer() runs after the hardware has completed a DMA\ntransfer but before the DMA completion interrupt has been handled, the\nserial core resets the transmit fifo while port-\u003etx_remaining still\ndescribes the old DMA transfer.\n\nA previous fix avoided advancing an empty fifo by checking that the fifo\nlength is at least tx_remaining. That still does not distinguish the old\nDMA payload from new bytes written after the flush. If userspace writes\nnew data before the stale DMA completion interrupt is handled, the fifo\ncan again contain at least tx_remaining bytes and the stale completion\ncan advance and discard those new bytes.\n\nMark an in-flight DMA transfer stale when the transmit fifo is flushed.\nThe later completion still unprepares the original DMA mapping using the\nsaved length, but it no longer advances the transmit fifo."
    }
  ],
  "id": "CVE-2026-93123",
  "lastModified": "2026-09-17T17:18:07.020",
  "metrics": {},
  "published": "2026-09-17T17:18:07.020",
  "references": [
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/231c84fe7ec40e4a06c398c0591d5b8e823d68e1"
    },
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/59faa59c25a0a098fbc86275408d7c8405015702"
    },
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/7ea38c49e7178960926657863299face6dc0e1b0"
    },
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/c02d030747c46da33faf406dd772ef91100efa27"
    }
  ],
  "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
  "vulnStatus": "Received"
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.





Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.


Detection rules are retrieved from Rulezet.


Related by attack behaviour

Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.