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-38586r8169: Fix possible ring buffer corruption on fragmented Tx packets.

Description

In the Linux kernel, the following vulnerability has been resolved: r8169: Fix possible ring buffer corruption on fragmented Tx packets. An issue was found on the RTL8125b when transmitting small fragmented packets, whereby invalid entries were inserted into the transmit ring buffer, subsequently leading to calls to dma_unmap_single() with a null address. This was caused by rtl8169_start_xmit() not noticing changes to nr_frags which may occur when small packets are padded (to work around hardware quirks) in rtl8169_tso_csum_v2(). To fix this, postpone inspecting nr_frags until after any padding has been applied.

Timeline

  1. ID reserved

    By Linux

  2. · 1 day later

    Published

  3. · 23 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-2024-38586, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.25% · top 83% of all CVEs (15 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: High 7.8.

Affected products

  • Linux · Linux

    • affected 9020845fb5d6bb4876a38fdf1259600e7d9a63d4 – < 61c1c98e2607120ce9c3fa1bf75e6da909712b27
    • affected 9020845fb5d6bb4876a38fdf1259600e7d9a63d4 – < b6d21cf40de103d63ae78551098a7c06af8c98dd
    • affected 9020845fb5d6bb4876a38fdf1259600e7d9a63d4 – < 0c48185a95309556725f818b82120bb74e9c627d
    • affected 9020845fb5d6bb4876a38fdf1259600e7d9a63d4 – < 68222d7b4b72aa321135cd453dac37f00ec41fd1
    • affected 9020845fb5d6bb4876a38fdf1259600e7d9a63d4 – < 078d5b7500d70af2de6b38e226b03f0b932026a6
    • affected 9020845fb5d6bb4876a38fdf1259600e7d9a63d4 – < 54e7a0d111240c92c0f02ceba6eb8f26bf6d6479
    • affected 9020845fb5d6bb4876a38fdf1259600e7d9a63d4 – < c71e3a5cffd5309d7f84444df03d5b72600cc417
  • Linux · Linux

    • affected 5.7
    • unaffected < 5.7
    • unaffected 5.10.221 – ≤ 5.10.*
    • unaffected 5.15.161 – ≤ 5.15.*
    • unaffected 6.1.93 – ≤ 6.1.*
    • unaffected 6.6.33 – ≤ 6.6.*
    • unaffected 6.8.12 – ≤ 6.8.*
    • unaffected 6.9.3 – ≤ 6.9.*
    • unaffected 6.10 – ≤ *

References

References7

Sources

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

Badge for a README or a ticket

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

Record last updated .