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-2023-54039can: j1939: j1939_tp_tx_dat_new(): fix out-of-bounds memory access

Description

In the Linux kernel, the following vulnerability has been resolved: can: j1939: j1939_tp_tx_dat_new(): fix out-of-bounds memory access In the j1939_tp_tx_dat_new() function, an out-of-bounds memory access could occur during the memcpy() operation if the size of skb->cb is larger than the size of struct j1939_sk_buff_cb. This is because the memcpy() operation uses the size of skb->cb, leading to a read beyond the struct j1939_sk_buff_cb. Updated the memcpy() operation to use the size of struct j1939_sk_buff_cb instead of the size of skb->cb. This ensures that the memcpy() operation only reads the memory within the bounds of struct j1939_sk_buff_cb, preventing out-of-bounds memory access. Additionally, add a BUILD_BUG_ON() to check that the size of skb->cb is greater than or equal to the size of struct j1939_sk_buff_cb. This ensures that the skb->cb buffer is large enough to hold the j1939_sk_buff_cb structure. [mkl: rephrase commit message]

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 5 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

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Deferred.

EPSS (exploitation in 30 days)
0.19% · top 91% of all CVEs (15 Nov 2026)
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected 9d71dd0c70099914fcd063135da3c580865e924c – < d2136f05690c272dfc9f9d6efcc51d5f53494b33
    • affected 9d71dd0c70099914fcd063135da3c580865e924c – < 70caa596d158a5d84b117f722d58f3ea503a5ba9
    • affected 9d71dd0c70099914fcd063135da3c580865e924c – < 4fe1d9b6231a68ffc91318f57fd8e4982f028cf7
    • affected 9d71dd0c70099914fcd063135da3c580865e924c – < 4c3fb22a6ec68258ee129a2e6b720f43dffc562f
    • affected 9d71dd0c70099914fcd063135da3c580865e924c – < 36befc9aed6202b4a9b906529aea13eacd7e34ff
    • affected 9d71dd0c70099914fcd063135da3c580865e924c – < b45193cb4df556fe6251b285a5ce44046dd36b4a
  • Linux · Linux

    • affected 5.4
    • unaffected < 5.4
    • unaffected 5.4.241 – ≤ 5.4.*
    • unaffected 5.10.178 – ≤ 5.10.*
    • unaffected 5.15.107 – ≤ 5.15.*
    • unaffected 6.1.24 – ≤ 6.1.*
    • unaffected 6.2.11 – ≤ 6.2.*
    • unaffected 6.3 – ≤ *

References

References6

Sources

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

Badge for a README or a ticket

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

Record last updated .