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-2025-38003can: bcm: add missing rcu read protection for procfs content

Description

In the Linux kernel, the following vulnerability has been resolved: can: bcm: add missing rcu read protection for procfs content When the procfs content is generated for a bcm_op which is in the process to be removed the procfs output might show unreliable data (UAF). As the removal of bcm_op's is already implemented with rcu handling this patch adds the missing rcu_read_lock() and makes sure the list entries are properly removed under rcu protection.

Timeline

  1. ID reserved

    By Linux

  2. · 53 days later

    Published

  3. · 14 months 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-2025-38003, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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.30% · top 77% of all CVEs (14 Nov 2026)
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected 5b48f5711f1c630841ab78dcc061de902f0e37bf – < 19f553a1ddf260da6570ed8f8d91a8c87f49b63a
    • affected 85cd41070df992d3c0dfd828866fdd243d3b774a – < 659701c0b954ccdb4a916a4ad59bbc16e726d42c
    • affected f34f2a18e47b73e48f90a757e1f4aaa8c7d665a1 – < 0622846db728a5332b917c797c733e202c4620ae
    • affected f1b4e32aca0811aa011c76e5d6cf2fa19224b386 – < 6d7d458c41b98a5c1670cbd36f2923c37de51cf5
    • affected f1b4e32aca0811aa011c76e5d6cf2fa19224b386 – < 1f912f8484e9c4396378c39460bbea0af681f319
    • affected f1b4e32aca0811aa011c76e5d6cf2fa19224b386 – < 63567ecd99a24495208dc860d50fb17440043006
    • affected f1b4e32aca0811aa011c76e5d6cf2fa19224b386 – < 7c9db92d5f0eadca30884af75c53d601edc512ee
    • affected f1b4e32aca0811aa011c76e5d6cf2fa19224b386 – < dac5e6249159ac255dad9781793dbe5908ac9ddb
    • affected fbac09a3b8890003c0c55294c00709f3ae5501bb
    • affected edb4baffb9483141a50fb7f7146cfe4a4c0c2db8
    • affected 5.4.205 – < 5.4.294
    • affected 5.10.130 – < 5.10.238
    • affected 5.15.54 – < 5.15.185
    • affected 4.19.252 – < 4.20
    • affected 5.18.11 – < 5.19
  • Linux · Linux

    • affected 5.19
    • unaffected < 5.19
    • unaffected 5.4.294 – ≤ 5.4.*
    • unaffected 5.10.238 – ≤ 5.10.*
    • unaffected 5.15.185 – ≤ 5.15.*
    • unaffected 6.1.141 – ≤ 6.1.*
    • unaffected 6.6.93 – ≤ 6.6.*
    • unaffected 6.12.31 – ≤ 6.12.*
    • unaffected 6.14.9 – ≤ 6.14.*
    • unaffected 6.15 – ≤ *

References

References10

Sources

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

Badge for a README or a ticket

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

Record last updated .