VulnerabilityPublished 23 Oct 2026

CVE-2026-98872: Linux kernel · freevxfs: don't BUG() on unknown typed-extent type

Source GCVE Database

Authoritative record:CVE-2026-98872· Medium

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

Data as of 26 Oct 2026, 12:55 UTC

Severity

Medium

Rated by Threat Radar · CVSS not yet scored by NVD

EPSS: 0.2% chance of exploitation in 30 days – higher than 11% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in fe40a19d571cbb584eea46038ee919d8712b2d2c, f1f2d54a576f0e4133b979e545abcfefd439c300, 1284d687d46953fff9c0d969df108114611aca8b +4

Exploitation evidence

Disclosed: evidence found.
CVE published 23 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.

ghsa-35fj-5v77-5rpx

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < fe40a19d571cbb584eea46038ee919d8712b2d2c	Fixed in fe40a19d571cbb584eea46038ee919d8712b2d2c
LinuxLinux	Affected ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < f1f2d54a576f0e4133b979e545abcfefd439c300	Fixed in f1f2d54a576f0e4133b979e545abcfefd439c300
LinuxLinux	Affected ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < 1284d687d46953fff9c0d969df108114611aca8b	Fixed in 1284d687d46953fff9c0d969df108114611aca8b
LinuxLinux	Affected ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < 704d48d81dc41470e108811c32c577ada66192d4	Fixed in 704d48d81dc41470e108811c32c577ada66192d4
LinuxLinux	Affected ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < 500e9d5bf9eff2096a21b7ac25a0a06ca46ab821	Fixed in 500e9d5bf9eff2096a21b7ac25a0a06ca46ab821
LinuxLinux	Affected ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < 405f13d7b270913e06e8e2b4de568985f94ef7d6	Fixed in 405f13d7b270913e06e8e2b4de568985f94ef7d6

AI-suggested

A fix is available that replaces the kernel BUG() call with WARN_ON_ONCE() and returns an error code to prevent kernel crashes. Users should update their Linux kernel to a version including this fix. Since no vendor advisory or patch link is provided, check the Linux kernel mailing lists or official kernel release notes for the patch and upgrade accordingly.

Description

A vulnerability in the Linux kernel's freevxfs filesystem code caused a kernel crash when encountering unknown typed-extent types during ioctl(FIBMAP) operations on regular files. The issue was due to the vxfs_bmap_typed() function calling BUG() on unexpected extent types, leading to a kernel panic. The vulnerability has been resolved by replacing the BUG() call with WARN_ON_ONCE() and returning 0 to fail cleanly without crashing the kernel.

References

Community reviews

Loading reviews…