VulnerabilityPublished 18 Oct 2026

CVE-2026-98592: Linux kernel · net: spacemit: clear TX descriptor on fragment mapping failure

Affects Linux kernelSource CVE Database V5

Not known to be exploited · fixed in ca9986cc824f2feb79b4a83e5f6f4c24c2140448 : update Linux kernel when convenient.

Data as of 26 Oct 2026, 14:05 UTC

Severity

Medium

Rated Medium by Threat Radar's AI analysis · CVSS not yet scored by NVD

EPSS: 0.1% chance of exploitation in 30 days – higher than 9% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in ca9986cc824f2feb79b4a83e5f6f4c24c2140448, 3001a103a367c6051c43aff363b6979c10e65347, 2d14720beb58870b15a52b236c3ab0be0e06e915

Exploitation evidence

Disclosed: evidence found.
CVE published 18 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade Linux kernel to ca9986cc824f2feb79b4a83e5f6f4c24c2140448, 3001a103a367c6051c43aff363b6979c10e65347 or 2d14720beb58870b15a52b236c3ab0be0e06e915.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ bfec6d7f2001c7470c3cd261ae65a3ba8737f226, < ca9986cc824f2feb79b4a83e5f6f4c24c2140448	Fixed in ca9986cc824f2feb79b4a83e5f6f4c24c2140448
LinuxLinux	Affected ≥ bfec6d7f2001c7470c3cd261ae65a3ba8737f226, < 3001a103a367c6051c43aff363b6979c10e65347	Fixed in 3001a103a367c6051c43aff363b6979c10e65347
LinuxLinux	Affected ≥ bfec6d7f2001c7470c3cd261ae65a3ba8737f226, < 2d14720beb58870b15a52b236c3ab0be0e06e915	Fixed in 2d14720beb58870b15a52b236c3ab0be0e06e915
LinuxLinux	Affected =6.18	Fixed in–

AI-suggested

A fix is available in the Linux kernel source identified by commits ca9986cc824f2feb79b4a83e5f6f4c24c2140448, 3001a103a367c6051c43aff363b6979c10e65347, and 2d14720beb58870b15a52b236c3ab0be0e06e915. Users should update to a Linux kernel version including these fixes to remediate the vulnerability.

Description

A vulnerability in the Linux kernel's spacemit network driver was fixed by ensuring TX descriptors are cleared on fragment mapping failure. Previously, if emac_tx_map_frag() failed on a fragment, the TX descriptor memory was left with stale DMA addresses while software considered the slot free, potentially causing the DMA engine to fetch unmapped addresses.

Impact

If exploited, this flaw could cause the DMA engine to fetch stale, unmapped addresses, potentially leading to data corruption or system instability. However, no known exploits are reported in the wild. The issue affects the Linux kernel version 6.18 specifically.

Summary

The Linux kernel spacemit driver had a flaw where emac_tx_mem_map() prematurely wrote ownership bits into TX descriptors before all buffer fragments were successfully mapped. On a fragment mapping failure, the cleanup path unmaps and drops the skb but does not clear the already-written descriptor memory, leaving TX_DESC_0_OWN set with stale DMA addresses. This mismatch could cause the DMA engine to access invalid memory when auto-advancing descriptors. The fix ensures that the TX descriptor is cleared on fragment mapping failure, aligning descriptor state with buffer mappings.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 26 Oct 2026, 10:22 UTC

Technical details

References

Community reviews

Related threats