VulnerabilityPublished 18 Oct 2026

CVE-2026-98632: Linux kernel · Bluetooth: mgmt: Dequeue pending mesh_send_sync entries on cancel

Source GCVE Database

Authoritative record:CVE-2026-98632· High

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

Data as of 26 Oct 2026, 14:05 UTC

Severity

High

Rated by Threat Radar · CVSS not yet scored by NVD

EPSS: 0.1% chance of exploitation in 30 days – higher than 6% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in f84e52829021d00bca8e067302f597c71af1f71a, 2189a219397d8e73808a67c4aade837b635705da, 718a8ffa180d469f99ad4f746f00cafd39456415 +3

Exploitation evidence

Disclosed: evidence found.
CVE published 18 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-qvq7-5mpj-hvwr

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ b338d91703fae6f6afd67f3f75caa3b8f36ddef3, < f84e52829021d00bca8e067302f597c71af1f71a	Fixed in f84e52829021d00bca8e067302f597c71af1f71a
LinuxLinux	Affected ≥ b338d91703fae6f6afd67f3f75caa3b8f36ddef3, < 2189a219397d8e73808a67c4aade837b635705da	Fixed in 2189a219397d8e73808a67c4aade837b635705da
LinuxLinux	Affected ≥ b338d91703fae6f6afd67f3f75caa3b8f36ddef3, < 718a8ffa180d469f99ad4f746f00cafd39456415	Fixed in 718a8ffa180d469f99ad4f746f00cafd39456415
LinuxLinux	Affected ≥ b338d91703fae6f6afd67f3f75caa3b8f36ddef3, < 084be90948632a5a358821e687b11a14445aae76	Fixed in 084be90948632a5a358821e687b11a14445aae76
LinuxLinux	Affected ≥ b338d91703fae6f6afd67f3f75caa3b8f36ddef3, < 71af682ba4692c2ed9ace4c3d4ca462ae368c029	Fixed in 71af682ba4692c2ed9ace4c3d4ca462ae368c029
LinuxLinux	Affected ≥ b338d91703fae6f6afd67f3f75caa3b8f36ddef3, < 03ced4687fb79286be7fdee0fc58d2c74de3e7bb	Fixed in 03ced4687fb79286be7fdee0fc58d2c74de3e7bb

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 to address this vulnerability by properly dequeuing pending mesh_send_sync entries before freeing associated objects and ensuring the transmission queue advances correctly after cancellation or errors. Users should apply the official Linux kernel updates that include this fix. Patch status is not explicitly stated; check the vendor or Linux kernel advisory for the current remediation guidance.

Description

A use-after-free vulnerability in the Linux kernel Bluetooth mesh management subsystem was resolved. The flaw occurs when a mesh transmission object is freed but a queued work entry retains a pointer to it, leading to use-after-free during later processing. The fix involves properly dequeuing pending entries before freeing and ensuring the transmission queue advances correctly to avoid deadlocks.

References

Community reviews

Loading reviews…