VulnerabilityPublished 18 Oct 2026

CVE-2026-98600: Linux kernel · Bluetooth: RFCOMM: Reject short EA=0 frames in rfcomm_recv_frame()

Source GCVE Database

Authoritative record:CVE-2026-98600· Medium

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

Data as of 26 Oct 2026, 17:16 UTC

Severity

Medium

Rated by Threat Radar · CVSS not yet scored by NVD

EPSS: 0.1% chance of exploitation in 30 days – higher than 7% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in c25587fa26761e623198b4f47151fe79d09ccde6, be00deee60044ffa820f9436415caeb665b2cda0, 97711b964877242933484989224a3c4c5d88a5ee +7

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-hpgr-cqmv-php2

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected >=6.12.111 <6.12.112 >=6.18.53 <6.18.55	Fixed in c25587fa26761e623198b4f47151fe79d09ccde6 be00deee60044ffa820f9436415caeb665b2cda0 97711b964877242933484989224a3c4c5d88a5ee 76876fd26569302d26d91cbe8b75fa8e66cf8969 9240fc1f2cde5331c61608da21b00394602ca762 71ccacde407b7d8f0ef48974a0d2524602fd5c44 7a1781a2f3a9667b3065d402d1f11986a2363e08 6d91041bb38b97e2feb625123cc0529d7b83a0e1 6.18.55 6.12.112
LinuxLinux	Affected =7.2	Fixed in–

AI-suggested

A fix has been applied to the Linux kernel to extend the length validation in rfcomm_recv_frame(). Users should update to the fixed kernel version once available. Patch status is not explicitly confirmed in the provided data; check the vendor advisory for current remediation guidance.

Description

A vulnerability in the Linux kernel's Bluetooth RFCOMM implementation was resolved. The flaw involved improper length checks for certain RFCOMM frames with extended length fields, allowing malformed frames to be processed incorrectly. This could lead to malformed data being treated as valid payload or control commands. The issue was fixed by enhancing the length validation logic in the rfcomm_recv_frame() function.

Impact

This vulnerability could allow malformed Bluetooth RFCOMM frames to be processed incorrectly by the Linux kernel, potentially leading to unexpected behavior in Bluetooth communication. However, no specific exploitation details or impacts such as privilege escalation or denial of service are described in the provided data.

Summary

The Linux kernel's Bluetooth RFCOMM code had a vulnerability where frames with an extended 2-byte length field and EA=0 were not properly validated for length. Specifically, rfcomm_recv_frame() checked that skb->len was at least sizeof(*hdr) + 1 (4 bytes), but frames requiring a 5-byte minimum length (sizeof(*hdr) + 2) passed this check incorrectly. This caused skb_pull() to fail silently, leaving a 3-byte header unprocessed and potentially misinterpreted as application payload or multiplexer control commands. The fix involved extending the length check to require skb->len >= sizeof(*hdr) + 2 when the extended length field is present.

References

Community reviews

Loading reviews…