VulnerabilityPublished 28 Oct 2026

CVE-2026-99132: Linux kernel · xfs: don't hold buffer locks across sync transaction commit in xfs_sync_sb_buf

Affects Linux kernelSource CVE Database V5

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

Data as of 28 Oct 2026, 10:58 UTC

Severity

Unrated

Rated by Threat Radar · CVSS not yet scored by NVD

Patch: Available – fixed in e5456dec79c71c8ef8f9f9adb77d320f113b34db, 6353e5cd8c43d6e805cacbfbfecf4103571a7ff8, 41a28c865d1d5843f8cb9e0af17a8f4d9e2961ff

Exploitation evidence

Disclosed: evidence found.
CVE published 28 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 e5456dec79c71c8ef8f9f9adb77d320f113b34db, 6353e5cd8c43d6e805cacbfbfecf4103571a7ff8 or 41a28c865d1d5843f8cb9e0af17a8f4d9e2961ff.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ f7664b31975bd893190708e76b2c424328f0c49b, < e5456dec79c71c8ef8f9f9adb77d320f113b34db	Fixed in e5456dec79c71c8ef8f9f9adb77d320f113b34db
LinuxLinux	Affected ≥ f7664b31975bd893190708e76b2c424328f0c49b, < 6353e5cd8c43d6e805cacbfbfecf4103571a7ff8	Fixed in 6353e5cd8c43d6e805cacbfbfecf4103571a7ff8
LinuxLinux	Affected ≥ f7664b31975bd893190708e76b2c424328f0c49b, < 41a28c865d1d5843f8cb9e0af17a8f4d9e2961ff	Fixed in 41a28c865d1d5843f8cb9e0af17a8f4d9e2961ff
LinuxLinux	Affected =4.18	Fixed in–

Description

In the Linux kernel, the following vulnerability has been resolved: xfs: don't hold buffer locks across sync transaction commit in xfs_sync_sb_buf xfs_sync_sb_buf() holds sb/rtsb buffer locks across a synchronous xfs_trans_commit(), which flushes the CIL push workqueue internally. If shutdown occurs during the CIL push, xfs_buf_item_unpin() needs to lock these buffers to fail them, causing a deadlock: setlabel: holds buf lock -> flush_workqueue(xfs-cil) CIL push worker: xfs_buf_item_unpin -> xfs_buf_lock(same buf) Remove the xfs_trans_bhold() calls so that commit releases the buffer locks normally. After the sync commit, re-acquire the buffers via mp->m_sb_bp / mp->m_rtsb_bp for the on-disk writeback.

References

Community reviews

Loading reviews…