Skip to main content
VulnerabilityPublished Updated

CVE-2026-98005: Linux kernel · erofs: delimit inode_share cache key components

Affects Linux kernelSource CVE Database V5

0

Not known to be exploited : upgrade to 16322a67336cfeea0af4b05206ef8d0e0eda55bb or 96bf9831fbf423b8104f7948cd8fe7007ecfb46c when convenient.

Data as of 26 Oct 2026, 12:55 UTC

Severity
Unrated

Rated by Threat Radar · CVSS not yet scored by NVD

EPSS
0.1% chance of exploitation in 30 days – higher than 4% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 16322a67336cfeea0af4b05206ef8d0e0eda55bb, 96bf9831fbf423b8104f7948cd8fe7007ecfb46c

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 25 Sep 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 16322a67336cfeea0af4b05206ef8d0e0eda55bb or 96bf9831fbf423b8104f7948cd8fe7007ecfb46c.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ e0bf7d1c074dc4252223ae897560345ccc24100d, < 16322a67336cfeea0af4b05206ef8d0e0eda55bb
Fixed in
  • 16322a67336cfeea0af4b05206ef8d0e0eda55bb
LinuxLinuxAffected
  • ≥ e0bf7d1c074dc4252223ae897560345ccc24100d, < 96bf9831fbf423b8104f7948cd8fe7007ecfb46c
Fixed in
  • 96bf9831fbf423b8104f7948cd8fe7007ecfb46c
LinuxLinuxAffected
  • =7.0
Fixed in–

Description

In the Linux kernel, the following vulnerability has been resolved: erofs: delimit inode_share cache key components Previously, inode_share keys were encoded as follows: fingerprint || domain_id It would be better to have a separator between the fingerprint and domain ID so that the fingerprint won't be parsed as part of a domain ID. Change the key encoding as follows: domain_id || '\0' || fingerprint Since domain_id is a NUL-terminated string, this makes the in-memory key indices unambiguous.

References

Community reviews

Loading reviews…