Skip to main content
VulnerabilityPublished

CVE-2026-99203: Linux kernel · pipe: preserve existing fasync readers on writer setup failure

Source GCVE Database

0
Authoritative record:CVE-2026-99203

Not known to be exploited · fixed in 2259809e5b7043c4ba20af7b14ba3e471cf55521 : patch Linux kernel soon.

Data as of 28 Oct 2026, 13:30 UTC

Severity
High

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

Patch
Available – fixed in 2259809e5b7043c4ba20af7b14ba3e471cf55521, 40bb03d3ea6f6a915218508819ecc4d7a7fa260d, 4c42ce499ce4b1c787e61082e3b13df4f30c4eaa

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 28 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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.

What to do

Upgrade Linux kernel to 2259809e5b7043c4ba20af7b14ba3e471cf55521, 40bb03d3ea6f6a915218508819ecc4d7a7fa260d or 4c42ce499ce4b1c787e61082e3b13df4f30c4eaa.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 76398425bb06b07cc3a3b1ce169c67dc9d6874ed, < 2259809e5b7043c4ba20af7b14ba3e471cf55521
Fixed in
  • 2259809e5b7043c4ba20af7b14ba3e471cf55521
LinuxLinuxAffected
  • ≥ 76398425bb06b07cc3a3b1ce169c67dc9d6874ed, < 40bb03d3ea6f6a915218508819ecc4d7a7fa260d
Fixed in
  • 40bb03d3ea6f6a915218508819ecc4d7a7fa260d
LinuxLinuxAffected
  • ≥ 76398425bb06b07cc3a3b1ce169c67dc9d6874ed, < 4c42ce499ce4b1c787e61082e3b13df4f30c4eaa
Fixed in
  • 4c42ce499ce4b1c787e61082e3b13df4f30c4eaa
LinuxLinuxAffected
  • =2.6.30
Fixed in–

AI-suggested

A fix for this vulnerability has been implemented in the Linux kernel to preserve existing asynchronous reader registrations on writer setup failure, preventing the use-after-free condition. Users should apply the official kernel updates that include this fix once available.

Description

A vulnerability in the Linux kernel's pipe implementation could lead to a use-after-free condition in the send_sigio() function. This occurs due to improper handling of asynchronous notification registrations when a writer setup fails, potentially causing a later pipe notification to dereference freed memory. The issue arises from the removal of a pre-existing reader entry during error handling, which clears asynchronous flags incorrectly while the writer entry remains registered.

References

Community reviews

Loading reviews…