CVE-2026-98290 (GCVE-0-2026-98290)
Vulnerability from cvelistv5 – Published: 2026-10-06 08:45 – Updated: 2026-10-07 06:49
VLAI
EPSS
VEX
Title
Bluetooth: RFCOMM: avoid socket lock inversion in listener cleanup
Summary
In the Linux kernel, the following vulnerability has been resolved:
Bluetooth: RFCOMM: avoid socket lock inversion in listener cleanup
rfcomm_sock_cleanup_listen() closes unaccepted child sockets through
rfcomm_sock_close(), which takes the child socket lock before
rfcomm_dlc_close() acquires rfcomm_mutex. The RFCOMM worker takes these
locks in reverse order while handling connections and DLC state changes,
so lockdep reports a possible deadlock.
Close dequeued children without taking their socket lock. The accept queue
owns a reference to each child, and bt_accept_dequeue() locks the child
while unlinking it and clearing its parent pointer.
Dropping the child lock makes it important to prevent a concurrent
rfcomm_connect_ind() from enqueueing a new child after cleanup observes an
empty queue. Set a listening socket to BT_CLOSED while its lock is still
held, before dropping the lock and draining the queue. The state check in
rfcomm_connect_ind() then rejects new children once cleanup starts.
Severity
7.5 (High)
Assigner
References
7 references
Impacted products
2 products
| Vendor | Product | Version | |
|---|---|---|---|
| Linux | Linux |
Affected:
b7ce436a5d798bc59e71797952566608a4b4626b , < eb4adaa46e4c9e6efa7be3ce06398f4d7c39b57c
(git)
Affected: b7ce436a5d798bc59e71797952566608a4b4626b , < 4aafb47301a799d3e01230d6568c4e93524e1523 (git) Affected: b7ce436a5d798bc59e71797952566608a4b4626b , < c741977e413f5b49d306700820fb55ccb8269f5a (git) Affected: b7ce436a5d798bc59e71797952566608a4b4626b , < c6792c441767256030606eb82dca5d5fc360dd9a (git) Affected: b7ce436a5d798bc59e71797952566608a4b4626b , < bfce253f039eb5f58b810af267942a9f59207254 (git) Affected: b7ce436a5d798bc59e71797952566608a4b4626b , < 18174b166547ef41973cc19feb5ef9cab39a8def (git) Affected: b7ce436a5d798bc59e71797952566608a4b4626b , < 801fb950cae7048eb7d83b18857d1ca37b8cd5a4 (git) |
|
| Linux | Linux |
Affected:
5.15
Unaffected: 0 , < 5.15 (semver) Unaffected: 5.15.222 , ≤ 5.15.* (semver) Unaffected: 6.1.189 , ≤ 6.1.* (semver) Unaffected: 6.6.158 , ≤ 6.6.* (semver) Unaffected: 6.12.112 , ≤ 6.12.* (semver) Unaffected: 6.18.54 , ≤ 6.18.* (semver) Unaffected: 7.2.8 , ≤ 7.2.* (semver) Unaffected: 7.3-rc4 , ≤ * (original_commit_for_fix) |
{
"containers": {
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"net/bluetooth/rfcomm/sock.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "eb4adaa46e4c9e6efa7be3ce06398f4d7c39b57c",
"status": "affected",
"version": "b7ce436a5d798bc59e71797952566608a4b4626b",
"versionType": "git"
},
{
"lessThan": "4aafb47301a799d3e01230d6568c4e93524e1523",
"status": "affected",
"version": "b7ce436a5d798bc59e71797952566608a4b4626b",
"versionType": "git"
},
{
"lessThan": "c741977e413f5b49d306700820fb55ccb8269f5a",
"status": "affected",
"version": "b7ce436a5d798bc59e71797952566608a4b4626b",
"versionType": "git"
},
{
"lessThan": "c6792c441767256030606eb82dca5d5fc360dd9a",
"status": "affected",
"version": "b7ce436a5d798bc59e71797952566608a4b4626b",
"versionType": "git"
},
{
"lessThan": "bfce253f039eb5f58b810af267942a9f59207254",
"status": "affected",
"version": "b7ce436a5d798bc59e71797952566608a4b4626b",
"versionType": "git"
},
{
"lessThan": "18174b166547ef41973cc19feb5ef9cab39a8def",
"status": "affected",
"version": "b7ce436a5d798bc59e71797952566608a4b4626b",
"versionType": "git"
},
{
"lessThan": "801fb950cae7048eb7d83b18857d1ca37b8cd5a4",
"status": "affected",
"version": "b7ce436a5d798bc59e71797952566608a4b4626b",
"versionType": "git"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"net/bluetooth/rfcomm/sock.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "5.15"
},
{
"lessThan": "5.15",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "5.15.*",
"status": "unaffected",
"version": "5.15.222",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.1.*",
"status": "unaffected",
"version": "6.1.189",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.6.*",
"status": "unaffected",
"version": "6.6.158",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.12.*",
"status": "unaffected",
"version": "6.12.112",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.18.*",
"status": "unaffected",
"version": "6.18.54",
"versionType": "semver"
},
{
"lessThanOrEqual": "7.2.*",
"status": "unaffected",
"version": "7.2.8",
"versionType": "semver"
},
{
"lessThanOrEqual": "*",
"status": "unaffected",
"version": "7.3-rc4",
"versionType": "original_commit_for_fix"
}
]
}
],
"cpeApplicability": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "5.15.222",
"versionStartIncluding": "5.15",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.1.189",
"versionStartIncluding": "5.15",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.6.158",
"versionStartIncluding": "5.15",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.12.112",
"versionStartIncluding": "5.15",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.18.54",
"versionStartIncluding": "5.15",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "7.2.8",
"versionStartIncluding": "5.15",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "7.3-rc4",
"versionStartIncluding": "5.15",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: RFCOMM: avoid socket lock inversion in listener cleanup\n\nrfcomm_sock_cleanup_listen() closes unaccepted child sockets through\nrfcomm_sock_close(), which takes the child socket lock before\nrfcomm_dlc_close() acquires rfcomm_mutex. The RFCOMM worker takes these\nlocks in reverse order while handling connections and DLC state changes,\nso lockdep reports a possible deadlock.\n\nClose dequeued children without taking their socket lock. The accept queue\nowns a reference to each child, and bt_accept_dequeue() locks the child\nwhile unlinking it and clearing its parent pointer.\n\nDropping the child lock makes it important to prevent a concurrent\nrfcomm_connect_ind() from enqueueing a new child after cleanup observes an\nempty queue. Set a listening socket to BT_CLOSED while its lock is still\nheld, before dropping the lock and draining the queue. The state check in\nrfcomm_connect_ind() then rejects new children once cleanup starts."
}
],
"metrics": [
{
"cvssV3_1": {
"baseScore": 7.5,
"baseSeverity": "HIGH",
"vectorString": "CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H",
"version": "3.1"
},
"scenarios": [
{
"lang": "en",
"value": "AV:A - A Bluetooth peer drives both halves of this bug. Its RFCOMM SABM creates a child in rfcomm_connect_ind(), and its later DISC makes krfcommd call rfcomm_sk_state_change() on that child (taking lock_sock(child) under rfcomm_mutex, and dereferencing bt_sk(child)-\u003eparent). Bluetooth requires radio range, so the vector is Adjacent.\nAC:H - The peer can send SABM and DISC at will, but both the ABBA deadlock and the late-enqueue window need the victim to close its listener at that moment. That window runs from rfcomm_sock_shutdown dropping the listener lock to cleanup_listen setting BT_CLOSED, and the peer cannot control when the application closes the socket.\nPR:N - rfcomm_connect_ind() only checks for a BT_LISTEN socket on the channel and for room in the backlog before it enqueues a child, so the peer needs no credentials.\nUI:N - No victim action beyond normal operation is needed. A service closing its RFCOMM listener on its own (exit, restart, or Bluetooth teardown) is a timing condition and is counted in AC:H.\nS:U - The deadlock and the dangling parent pointer both stay inside kernel RFCOMM socket state and do not cross a virtualization or hardware boundary.\nC:H - A child enqueued after the drain keeps bt_sk(sk)-\u003eparent pointing at the listener, but bt_accept_enqueue takes no reference on it, so rfcomm_sock_kill frees the listener while the pointer is still live. A later state change then reads the freed sock through parent-\u003esk_data_ready, a use-after-free that can be groomed for disclosure.\nI:H - On the peer\u0027s DISC, rfcomm_sk_state_change calls bt_accept_unlink(), which does list_del on the freed listener\u0027s accept_q and decrements its backlog, then makes an indirect call through the freed parent-\u003esk_data_ready. That is a write to freed memory and a call through a function pointer an attacker can replace.\nA:H - The ABBA blocks krfcommd forever while it holds rfcomm_mutex (rfcomm_dlc_close in the closer against lock_sock(child) in rfcomm_sk_state_change). That stops all RFCOMM processing and hangs the closing task, and the use-after-free path can oops the kernel."
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-10-07T06:49:55.796Z",
"orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"shortName": "Linux"
},
"references": [
{
"url": "https://git.kernel.org/stable/c/eb4adaa46e4c9e6efa7be3ce06398f4d7c39b57c"
},
{
"url": "https://git.kernel.org/stable/c/4aafb47301a799d3e01230d6568c4e93524e1523"
},
{
"url": "https://git.kernel.org/stable/c/c741977e413f5b49d306700820fb55ccb8269f5a"
},
{
"url": "https://git.kernel.org/stable/c/c6792c441767256030606eb82dca5d5fc360dd9a"
},
{
"url": "https://git.kernel.org/stable/c/bfce253f039eb5f58b810af267942a9f59207254"
},
{
"url": "https://git.kernel.org/stable/c/18174b166547ef41973cc19feb5ef9cab39a8def"
},
{
"url": "https://git.kernel.org/stable/c/801fb950cae7048eb7d83b18857d1ca37b8cd5a4"
}
],
"title": "Bluetooth: RFCOMM: avoid socket lock inversion in listener cleanup",
"x_generator": {
"engine": "bippy-1.2.0"
}
}
},
"cveMetadata": {
"assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"assignerShortName": "Linux",
"cveId": "CVE-2026-98290",
"datePublished": "2026-10-06T08:45:50.299Z",
"dateReserved": "2026-09-25T10:25:14.336Z",
"dateUpdated": "2026-10-07T06:49:55.796Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2",
"vulnerability-lookup:meta": {
"epss": {
"cve": "CVE-2026-98290",
"date": "2026-10-22",
"epss": "0.00257",
"percentile": "0.16409"
},
"microsoft_vex": {
"current_release_date": "2026-10-21T18:37:25.000Z",
"cve": "CVE-2026-98290",
"id": "msrc_CVE-2026-98290",
"initial_release_date": "2026-10-07T01:28:27.000Z",
"product_status:fixed": "1",
"product_status:known_affected": "1",
"product_status:under_investigation": "1",
"source": "Microsoft CSAF VEX",
"status": "final",
"title": "Bluetooth: RFCOMM: avoid socket lock inversion in listener cleanup",
"url": "https://msrc.microsoft.com/csaf/vex/2026/msrc_cve-2026-98290.json",
"version": "4"
},
"nvd": {
"cve": {
"affected": [
{
"affectedData": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"net/bluetooth/rfcomm/sock.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "eb4adaa46e4c9e6efa7be3ce06398f4d7c39b57c",
"status": "affected",
"version": "b7ce436a5d798bc59e71797952566608a4b4626b",
"versionType": "git"
},
{
"lessThan": "4aafb47301a799d3e01230d6568c4e93524e1523",
"status": "affected",
"version": "b7ce436a5d798bc59e71797952566608a4b4626b",
"versionType": "git"
},
{
"lessThan": "c741977e413f5b49d306700820fb55ccb8269f5a",
"status": "affected",
"version": "b7ce436a5d798bc59e71797952566608a4b4626b",
"versionType": "git"
},
{
"lessThan": "c6792c441767256030606eb82dca5d5fc360dd9a",
"status": "affected",
"version": "b7ce436a5d798bc59e71797952566608a4b4626b",
"versionType": "git"
},
{
"lessThan": "bfce253f039eb5f58b810af267942a9f59207254",
"status": "affected",
"version": "b7ce436a5d798bc59e71797952566608a4b4626b",
"versionType": "git"
},
{
"lessThan": "18174b166547ef41973cc19feb5ef9cab39a8def",
"status": "affected",
"version": "b7ce436a5d798bc59e71797952566608a4b4626b",
"versionType": "git"
},
{
"lessThan": "801fb950cae7048eb7d83b18857d1ca37b8cd5a4",
"status": "affected",
"version": "b7ce436a5d798bc59e71797952566608a4b4626b",
"versionType": "git"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"net/bluetooth/rfcomm/sock.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "5.15"
},
{
"lessThan": "5.15",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "5.15.*",
"status": "unaffected",
"version": "5.15.222",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.1.*",
"status": "unaffected",
"version": "6.1.189",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.6.*",
"status": "unaffected",
"version": "6.6.158",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.12.*",
"status": "unaffected",
"version": "6.12.112",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.18.*",
"status": "unaffected",
"version": "6.18.54",
"versionType": "semver"
},
{
"lessThanOrEqual": "7.2.*",
"status": "unaffected",
"version": "7.2.8",
"versionType": "semver"
},
{
"lessThanOrEqual": "*",
"status": "unaffected",
"version": "7.3",
"versionType": "original_commit_for_fix"
}
]
}
],
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
],
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: RFCOMM: avoid socket lock inversion in listener cleanup\n\nrfcomm_sock_cleanup_listen() closes unaccepted child sockets through\nrfcomm_sock_close(), which takes the child socket lock before\nrfcomm_dlc_close() acquires rfcomm_mutex. The RFCOMM worker takes these\nlocks in reverse order while handling connections and DLC state changes,\nso lockdep reports a possible deadlock.\n\nClose dequeued children without taking their socket lock. The accept queue\nowns a reference to each child, and bt_accept_dequeue() locks the child\nwhile unlinking it and clearing its parent pointer.\n\nDropping the child lock makes it important to prevent a concurrent\nrfcomm_connect_ind() from enqueueing a new child after cleanup observes an\nempty queue. Set a listening socket to BT_CLOSED while its lock is still\nheld, before dropping the lock and draining the queue. The state check in\nrfcomm_connect_ind() then rejects new children once cleanup starts."
}
],
"id": "CVE-2026-98290",
"lastModified": "2026-10-19T10:18:30.680",
"metrics": {
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "HIGH",
"attackVector": "ADJACENT_NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 7.5,
"baseSeverity": "HIGH",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H",
"version": "3.1"
},
"exploitabilityScore": 1.6,
"impactScore": 5.9,
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"type": "Secondary"
}
]
},
"published": "2026-10-06T09:18:19.317",
"references": [
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/18174b166547ef41973cc19feb5ef9cab39a8def"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/4aafb47301a799d3e01230d6568c4e93524e1523"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/801fb950cae7048eb7d83b18857d1ca37b8cd5a4"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/bfce253f039eb5f58b810af267942a9f59207254"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/c6792c441767256030606eb82dca5d5fc360dd9a"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/c741977e413f5b49d306700820fb55ccb8269f5a"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/eb4adaa46e4c9e6efa7be3ce06398f4d7c39b57c"
}
],
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"vulnStatus": "Received"
}
},
"redhat_vex": {
"aggregate_severity": "Moderate",
"current_release_date": "2026-10-10T23:25:20+00:00",
"cve": "CVE-2026-98290",
"id": "CVE-2026-98290",
"initial_release_date": "2026-10-06T00:00:00+00:00",
"product_status:known_affected": "248",
"product_status:known_not_affected": "29",
"source": "Red Hat CSAF VEX",
"status": "final",
"title": "kernel: Bluetooth: RFCOMM: avoid socket lock inversion in listener cleanup",
"url": "https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-98290.json",
"version": "3"
},
"suse_vex": {
"aggregate_severity": "moderate",
"current_release_date": "2026-10-07T16:28:07Z",
"cve": "CVE-2026-98290",
"id": "CVE-2026-98290",
"initial_release_date": "2026-10-07T16:28:07Z",
"product_status:known_affected": "84",
"product_status:known_not_affected": "263",
"source": "SUSE CSAF VEX",
"status": "interim",
"title": "SUSE CVE CVE-2026-98290",
"url": "https://ftp.suse.com/pub/projects/security/csaf-vex/2026/cve-2026-98290.json",
"version": "2"
}
}
}
Loading…
Loading…
Experimental. This forecast is provided for visualization only and may change without notice. Do not use it for operational decisions.
Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Loading…
Loading…
The MITRE ATT&CK techniques below are AI-generated suggestions, inferred from the description of the
vulnerability by the CIRCL/vulnerability-attack-technique-classification-roberta-base
model, served locally by ML-Gateway.
They have not been verified by an analyst and are provided for guidance only.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Loading…
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.
Loading…