Answer in brief
CVE-2023-53827 records a High severity (CVSS 8.8) vulnerability in Bluetooth: L2CAP: Fix use-after-free in l2cap_disconnect_{req,rsp}. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2023-53827 records a High severity (CVSS 8.8) vulnerability in Bluetooth: L2CAP: Fix use-after-free in l2cap_disconnect_{req,rsp}. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 8.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=61d6ef3e3408cdf7e622646fb90a9f7f9560b943 <f2d38e77aa5f3effc143e7dd24da8acf02925958 || >=61d6ef3e3408cdf7e622646fb90a9f7f9560b943 <1351551aa9058e07a20a27a158270cf84fcde621 || >=61d6ef3e3408cdf7e622646fb90a9f7f9560b943 <c02421992505c95c7f3c9ad59ee35e22eac60988 || >=61d6ef3e3408cdf7e622646fb90a9f7f9560b943 <d9ba36c22a7bb09d6bac4cc2f243eff05da53f43 || >=61d6ef3e3408cdf7e622646fb90a9f7f9560b943 <ac6725a634f7e8c0330610a8527f20c730b61115 || >=61d6ef3e3408cdf7e622646fb90a9f7f9560b943 <348d446762e7c70778df8bafbdf3fa0df2123f58 || >=61d6ef3e3408cdf7e622646fb90a9f7f9560b943 <d82a439c3cfdb28aa7e82e2e849c5c4dd9fca284 || >=61d6ef3e3408cdf7e622646fb90a9f7f9560b943 <a2a9339e1c9deb7e1e079e12e27a0265aea8421a | f2d38e77aa5f3effc143e7dd24da8acf02925958, 1351551aa9058e07a20a27a158270cf84fcde621, c02421992505c95c7f3c9ad59ee35e22eac60988, d9ba36c22a7bb09d6bac4cc2f243eff05da53f43, ac6725a634f7e8c0330610a8527f20c730b61115, 348d446762e7c70778df8bafbdf3fa0df2123f58, d82a439c3cfdb28aa7e82e2e849c5c4dd9fca284, a2a9339e1c9deb7e1e079e12e27a0265aea8421a |
| Linux/Linuxgeneric | 3.5 | Not reported |
Published upstream
Dec 9, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 4, 2026
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: Fix use-after-free in l2cap_disconnect_{req,rsp} Similar to commit d0be8347c623 ("Bluetooth: L2CAP: Fix use-after-free caused by l2cap_chan_put"), just use l2cap_chan_hold_unless_zero to prevent referencing a channel that is about to be destroyed.
Quoted source text, attributed separately from HOL analysis.
CVSS is 8.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=61d6ef3e3408cdf7e622646fb90a9f7f9560b943 <f2d38e77aa5f3effc143e7dd24da8acf02925958 || >=61d6ef3e3408cdf7e622646fb90a9f7f9560b943 <1351551aa9058e07a20a27a158270cf84fcde621 || >=61d6ef3e3408cdf7e622646fb90a9f7f9560b943 <c02421992505c95c7f3c9ad59ee35e22eac60988 || >=61d6ef3e3408cdf7e622646fb90a9f7f9560b943 <d9ba36c22a7bb09d6bac4cc2f243eff05da53f43 || >=61d6ef3e3408cdf7e622646fb90a9f7f9560b943 <ac6725a634f7e8c0330610a8527f20c730b61115 || >=61d6ef3e3408cdf7e622646fb90a9f7f9560b943 <348d446762e7c70778df8bafbdf3fa0df2123f58 || >=61d6ef3e3408cdf7e622646fb90a9f7f9560b943 <d82a439c3cfdb28aa7e82e2e849c5c4dd9fca284 || >=61d6ef3e3408cdf7e622646fb90a9f7f9560b943 <a2a9339e1c9deb7e1e079e12e27a0265aea8421a | f2d38e77aa5f3effc143e7dd24da8acf02925958, 1351551aa9058e07a20a27a158270cf84fcde621, c02421992505c95c7f3c9ad59ee35e22eac60988, d9ba36c22a7bb09d6bac4cc2f243eff05da53f43, ac6725a634f7e8c0330610a8527f20c730b61115, 348d446762e7c70778df8bafbdf3fa0df2123f58, d82a439c3cfdb28aa7e82e2e849c5c4dd9fca284, a2a9339e1c9deb7e1e079e12e27a0265aea8421a |
| Linux/Linuxgeneric | 3.5 | Not reported |
Published upstream
Dec 9, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 4, 2026
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: Fix use-after-free in l2cap_disconnect_{req,rsp} Similar to commit d0be8347c623 ("Bluetooth: L2CAP: Fix use-after-free caused by l2cap_chan_put"), just use l2cap_chan_hold_unless_zero to prevent referencing a channel that is about to be destroyed.
Quoted source text, attributed separately from HOL analysis.