CVE-2024-53058: net: stmmac: TSO: Fix unbalanced DMA map/unmap for non-paged SKB data
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.60% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 07c9c26e37542486e34d767505e842f48f29c3f6, 58d23d835eb498336716cca55b5714191a309286, 66600fac7a984dea4ae095411f644770b2561ede; azl3 kernel 6.6.57.1-7 on Azure Linux 3.0 6.6.64.2-1; azl3 kernel 6.6.64.2-1 on Azure Linux 3.0 6.6.64.2-1.
- Severity is disputed: the assigning authority (CNA) scores it 9.4, NVD 5.5.
Low priority for now. Upgrade to Linux Linux 07c9c26e37542486e34d767505e842f48f29c3f6, 58d23d835eb498336716cca55b5714191a309286, 66600fac7a984dea4ae095411f644770b2561ede; azl3 kernel 6.6.57.1-7 on Azure Linux 3.0 6.6.64.2-1; azl3 kernel 6.6.64.2-1 on Azure Linux 3.0 6.6.64.2-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In the Linux kernel, the following vulnerability has been resolved: net: stmmac: TSO: Fix unbalanced DMA map/unmap for non-paged SKB data In case the non-paged data of a SKB carries protocol header and protocol payload to be transmitted on a certain platform that the DMA AXI address width is configured to 40-bit/48-bit, or the size of the non-paged data is bigger than TSO_MAX_BUFF_SIZE on a certain platform that the DMA AXI address width is configured to 32-bit, then this SKB requires at least two DMA transmit descriptors to serve it. For example, three descriptors are allocated to split one DMA buffer mapped from one piece of non-paged data: dma_desc[N + 0], dma_desc[N + 1], dma_desc[N + 2]. Then three elements of tx_q->tx_skbuff_dma[] will be allocated to hold extra information to be reused in stmmac_tx_clean(): tx_q->tx_skbuff_dma[N + 0], tx_q->tx_skbuff_dma[N + 1], tx_q->tx_skbuff_dma[N + 2]. Now we focus on tx_q->tx_skbuff_dma[entry].buf, which is the DMA buffer address returned by DMA mapping call. stmmac_tx_clean() will try to unmap the DMA buffer _ONLY_IF_ tx_q->tx_skbuff_dma[entry].buf is a valid buffer address. The expected behavior that saves DMA buffer address of this non-paged data to tx_q->tx_skbuff_dma[entry].buf is: tx_q->tx_skbuff_dma[N + 0].buf = NULL; tx_q->tx_skbuff_dma[N + 1].buf = NULL; tx_q->tx_skbuff_dma[N + 2].buf = dma_map_single(); Unfortunately, the current code misbehaves like this: tx_q->tx_skbuff_dma[N + 0].buf = dma_map_single(); tx_q->tx_skbuff_dma[N + 1].buf = NULL; tx_q->tx_skbuff_dma[N + 2].buf = NULL; On the stmmac_tx_clean() side, when dma_desc[N + 0] is closed by the DMA engine, tx_q->tx_skbuff_dma[N + 0].buf is a valid buffer address obviously, then the DMA buffer will be unmapped immediately. There may be a rare case that the DMA engine does not finish the pending dma_desc[N + 1], dma_desc[N + 2] yet. Now things will go horribly wrong, DMA is going to access a unmapped/unreferenced memory region, corrupted data will be transmited or iommu fault will be triggered :( In contrast, the for-loop that maps SKB fragments behaves perfectly as expected, and that is how the driver should do for both non-paged data and paged frags actually. This patch corrects DMA map/unmap sequences by fixing the array index for tx_q->tx_skbuff_dma[entry].buf when assigning DMA buffer address. Tested and verified on DWXGMAC CORE 3.20a
- Published
- Nov 19, 2024
- Updated
- Aug 5, 2026
- EPSS
- 0.6% · 49th percentile
- CWE
- —
Report tools
Action score
22
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.6%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 5.5
- CNA · Linux
- 9.4
- 3.9 point gap
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:H
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 4.7affected
- f748be531d7012c456b97f66091d86b3675c5fef and later · before ece593fc9c00741b682869d3f3dc584d37b7c9dfaffected · git
- f748be531d7012c456b97f66091d86b3675c5fef and later · before a3ff23f7c3f0e13f718900803e090fd3997d6bc9affected · git
- f748be531d7012c456b97f66091d86b3675c5fef and later · before 07c9c26e37542486e34d767505e842f48f29c3f6affected · git
- f748be531d7012c456b97f66091d86b3675c5fef and later · before 58d23d835eb498336716cca55b5714191a309286affected · git
- f748be531d7012c456b97f66091d86b3675c5fef and later · before 66600fac7a984dea4ae095411f644770b2561edeaffected · git
- before 4.7not affected · semver
- 5.15.171 and later · up to and including 5.15.*not affected · semver
- 6.1.116 and later · up to and including 6.1.*not affected · semver
- 6.6.60 and later · up to and including 6.6.*not affected · semver
Affected versions · NVD (5)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel4.7 and later · before 5.15.171
- linux linux kernel5.16 and later · before 6.1.116
- linux linux kernel6.2 and later · before 6.6.60
- linux linux kernel6.7 and later · before 6.11.7
- linux linux kernel6.12
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.119-1 | 6.1.119-1 |
| Debian:13 | linux | before 6.11.7-1 | 6.11.7-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2024-53053Nov 19, 2024 · scsi: ufs: core: Fix another deadlock during RTC update22Monitor
- ← EarlierCVE-2024-53055Nov 19, 2024 · wifi: iwlwifi: mvm: fix 6 GHz scan construction22Monitor
- Later →CVE-2024-53060Nov 19, 2024 · drm/amdgpu: prevent NULL pointer dereference if ATIF is not supported22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 07c9c26e37542486e34d767505e842f48f29c3f6 | Vendor (CNA) |
| Linux Linux | 58d23d835eb498336716cca55b5714191a309286 | Vendor (CNA) |
| Linux Linux | 66600fac7a984dea4ae095411f644770b2561ede | Vendor (CNA) |
| Linux Linux | a3ff23f7c3f0e13f718900803e090fd3997d6bc9 | Vendor (CNA) |
| Linux Linux | ece593fc9c00741b682869d3f3dc584d37b7c9df | Vendor (CNA) |
| azl3 kernel 6.6.57.1-7 on Azure Linux 3.0 | 6.6.64.2-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| azl3 kernel 6.6.64.2-1 on Azure Linux 3.0 | 6.6.64.2-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 kernel 5.15.167.1-2 on CBL Mariner 2.0 | 5.15.173.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 kernel 5.15.167.1-2 on CBL-Mariner 2.0 | 5.15.173.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 kernel 5.15.173.1-1 on CBL Mariner 2.0 | 5.15.173.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| debian:linux | 6.1.119-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/58d23d835eb498336716cca55b5714191a309286
- git.kernel.org/stable/c/66600fac7a984dea4ae095411f644770b2561ede
- git.kernel.org/stable/c/a3ff23f7c3f0e13f718900803e090fd3997d6bc9
- git.kernel.org/stable/c/ece593fc9c00741b682869d3f3dc584d37b7c9df
- lists.debian.org/debian-lts-announce/2025/01/msg00001.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.