Skip to main content

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: mgmt: fix race in read_unconf_index_list() read_unconf_index_list()… (CVE-2026-98456)

0
Medium
Published: 10/18/2026 (10/18/2026, 18:31:49 UTC)
Source: GCVE Database

Description

A race condition vulnerability in the Linux kernel's Bluetooth management subsystem was resolved. The flaw involved the read_unconf_index_list() function, which could cause an out-of-bounds write due to inconsistent counting and filling of unconfigured Bluetooth controllers during asynchronous setup. The fix involves allocating space for every device on the hci_dev_list to prevent size mismatches caused by flag changes during the operation.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 10/18/2026, 20:03:16 UTC

Technical Analysis

The vulnerability in the Linux kernel Bluetooth management code arises from a race condition in read_unconf_index_list(). This function first counts unconfigured controllers to allocate response space, then rechecks device flags while filling the response. Because hci_dev_list_lock only stabilizes list membership but does not serialize per-device flags, asynchronous controller setup can change flags between counting and filling passes. This leads to a controller being omitted from the allocation count but included in the fill pass, causing an out-of-bounds write to the response index array. The patch fixes this by allocating space for every device on the hci_dev_list, ensuring the response buffer is always large enough regardless of flag transitions, while still reporting counts only for eligible unconfigured controllers.

Potential Impact

The vulnerability could cause an out-of-bounds write in kernel memory during Bluetooth controller enumeration, potentially leading to memory corruption or system instability. No known exploits in the wild have been reported. The impact is limited to systems running the affected Linux kernel Bluetooth management code during asynchronous controller setup.

Mitigation Recommendations

A fix has been implemented in the Linux kernel to address this race condition by changing the allocation strategy in read_unconf_index_list(). Users should apply the official Linux kernel updates that include this patch to remediate the vulnerability. Since this is a kernel-level issue, updating to a patched kernel version is the recommended mitigation.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Gcve Source
db.gcve.eu
Osv Id
GHSA-79jp-j4mv-p57c
Osv Schema Version
1.4.0
Aliases
["CVE-2026-98456"]

Threat ID: 6ad520b12cdf04f656993b18

Added to database: 10/18/2026, 19:40:33 UTC

Last enriched: 10/18/2026, 20:03:16 UTC

Last updated: 10/18/2026, 22:02:57 UTC

Views: 7

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses