VulnerabilityPublished 17 Sep 2026Updated 20 Oct 2026

CVE-2026-93140: Linux kernel · udf: Mark LVID buffer as uptodate before marking it dirty

Affects Linux kernelSource GCVE Database

Authoritative record:CVE-2026-93140· Low

Not known to be exploited.

Data as of 26 Oct 2026, 17:16 UTC

Severity

Low

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.

Exploitation evidence

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

Affected software

Product	Affected	Fixed in
Ubuntu 26.04 LTSlinux`pkg:deb/ubuntu/linux?arch=source&distro=resolute`Other threats	Affected 6.17.0-5.5 – 7.0.0-38.38 23 affected builds	Fixed in–
Ubuntu 26.04 LTSlinux-aws`pkg:deb/ubuntu/linux-aws?arch=source&distro=resolute`Other threats	Affected 6.17.0-1002.2 – 7.0.0-1014.14 15 affected builds	Fixed in–
Ubuntu 26.04 LTSlinux-azure`pkg:deb/ubuntu/linux-azure?arch=source&distro=resolute`Other threats	Affected 6.17.0-1003.3 – 7.0.0-1017.17 15 affected builds	Fixed in–
Ubuntu 26.04 LTSlinux-azure-fde`pkg:deb/ubuntu/linux-azure-fde?arch=source&distro=resolute`Other threats	Affected 7.0.0-1003.3 – 7.0.0-1016.16 9 affected builds	Fixed in–
Ubuntu 26.04 LTSlinux-gcp`pkg:deb/ubuntu/linux-gcp?arch=source&distro=resolute`Other threats	Affected 6.17.0-1002.2 – 7.0.0-1014.14 13 affected builds	Fixed in–
Ubuntu 26.04 LTSlinux-gke`pkg:deb/ubuntu/linux-gke?arch=source&distro=resolute`Other threats	Affected 7.0.0-1002.3 – 7.0.0-1008.9 6 affected builds	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix has been implemented in the Linux kernel source code to mark the LVID buffer as uptodate before marking it dirty, preventing spurious warnings. Users should update to a Linux kernel version that includes this fix. Patch status is not explicitly stated in the provided data; therefore, verify the vendor advisory or kernel changelogs for the exact fixed versions and apply updates accordingly.

Description

A vulnerability in the Linux kernel's UDF filesystem code caused spurious warnings due to improper handling of the Logical Volume Integrity Descriptor (LVID) buffer's uptodate flag after an I/O error. This was fixed by ensuring the buffer is marked uptodate before marking it dirty, preventing warnings during subsequent filesystem operations.

Impact

This vulnerability causes spurious kernel warnings (WARN_ON_ONCE) during UDF filesystem operations after certain I/O errors. It does not indicate data corruption or security compromise but may cause unnecessary kernel warnings and potential confusion during debugging or system monitoring.

Summary

The Linux kernel UDF filesystem had a flaw where, after an I/O error writing the LVID buffer, the buffer's BH_Uptodate flag was cleared despite the in-memory data remaining valid. Subsequent operations that modified the LVID buffer and marked it dirty triggered spurious WARN_ON_ONCE warnings because the buffer was not marked uptodate. The fix unconditionally sets the BH_Uptodate flag before marking the buffer dirty in udf_open_lvid() and udf_sync_fs(), aligning with a previous fix in udf_close_lvid(), thus ensuring consistent behavior across all LVID updates.

GCVE source: db.gcve.eu
OSV ID: UBUNTU-CVE-2026-93140
Osv Schema Version: 1.7.0
Ecosystems: Ubuntu:Pro:14.04:LTS, Ubuntu:Pro:16.04:LTS, Ubuntu:16.04:LTS, Ubuntu:Pro:FIPS:16.04:LTS, Ubuntu:Pro:18.04:LTS, Ubuntu:18.04:LTS, Ubuntu:Pro:FIPS-updates:18.04:LTS, Ubuntu:Pro:FIPS:18.04:LTS, Ubuntu:Pro:20.04:LTS, Ubuntu:20.04:LTS, Ubuntu:Pro:FIPS-updates:20.04:LTS, Ubuntu:Pro:FIPS:20.04:LTS, Ubuntu:22.04:LTS, Ubuntu:Nvidia-BlueField:22.04:LTS, Ubuntu:Pro:FIPS-preview:22.04:LTS, Ubuntu:Pro:FIPS-updates:22.04:LTS, Ubuntu:Pro:Realtime:22.04:LTS, Ubuntu:24.04:LTS, Ubuntu:Nvidia-BlueField:24.04:LTS, Ubuntu:Pro:FIPS-updates:24.04:LTS, Ubuntu:Pro:Realtime:24.04:LTS, Ubuntu:26.04:LTS

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 24 Oct 2026, 23:56 UTC

Technical details

References

Community reviews

Related threats