Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2024-26903Bluetooth: rfcomm: Fix null-ptr-deref in rfcomm_check_security

Description

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: rfcomm: Fix null-ptr-deref in rfcomm_check_security During our fuzz testing of the connection and disconnection process at the RFCOMM layer, we discovered this bug. By comparing the packets from a normal connection and disconnection process with the testcase that triggered a KASAN report. We analyzed the cause of this bug as follows: 1. In the packets captured during a normal connection, the host sends a `Read Encryption Key Size` type of `HCI_CMD` packet (Command Opcode: 0x1408) to the controller to inquire the length of encryption key.After receiving this packet, the controller immediately replies with a Command Completepacket (Event Code: 0x0e) to return the Encryption Key Size. 2. In our fuzz test case, the timing of the controller's response to this packet was delayed to an unexpected point: after the RFCOMM and L2CAP layers had disconnected but before the HCI layer had disconnected. 3. After receiving the Encryption Key Size Response at the time described in point 2, the host still called the rfcomm_check_security function. However, by this time `struct l2cap_conn *conn = l2cap_pi(sk)->chan->conn;` had already been released, and when the function executed `return hci_conn_security(conn->hcon, d->sec_level, auth_type, d->out);`, specifically when accessing `conn->hcon`, a null-ptr-deref error occurred. To fix this bug, check if `sk->sk_state` is BT_CLOSED before calling rfcomm_recv_frame in rfcomm_process_rx.

Timeline

  1. ID reserved

    By Linux

  2. · 58 days later

    Published

  3. · 2 years later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2024-26903, by who scored it
Scored byCVSSScoreVector
CISA-ADPADP (enrichment)3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.28% · top 79% of all CVEs (17 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 369f419c097e82407dd429a202cde9a73d3ae29b
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 5f369efd9d963c1f711a06c9b8baf9f5ce616d85
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 81d7d920a22fd58ef9aedb1bd0a68ee32bd23e96
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 8d1753973f598531baaa2c1033cf7f7b5bb004b0
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 567c0411dc3b424fc7bd1e6109726d7ba32d4f73
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 3ead59bafad05f2967ae2438c0528d53244cfde5
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 5f9fe302dd3a9bbc50f4888464c1773f45166bfd
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 2535b848fa0f42ddff3e5255cf5e742c9b77bb26
  • Linux · Linux

    • affected 2.6.12
    • unaffected < 2.6.12
    • unaffected 4.19.311 – ≤ 4.19.*
    • unaffected 5.4.273 – ≤ 5.4.*
    • unaffected 5.10.214 – ≤ 5.10.*
    • unaffected 5.15.153 – ≤ 5.15.*
    • unaffected 6.1.83 – ≤ 6.1.*
    • unaffected 6.6.23 – ≤ 6.6.*
    • unaffected 6.7.11 – ≤ 6.7.*
    • unaffected 6.8 – ≤ *

References

References11

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2024-26903 badge
[![CVE-2024-26903](https://cveledger.app/badge/CVE-2024-26903.svg)](https://cveledger.app/cve/CVE-2024-26903)

Record last updated .