net: macb: Shuffle the tx ring before enabling tx
In the Linux kernel, the following vulnerability has been resolved: net: macb: Shuffle the tx ring before enabling tx Quanyang observed that when using an NFS rootfs on an AMD ZynqMp board, the rootfs may take an extended time to recover after a suspend. Upon investigation, it was determined that the issue originates from a problem in the macb driver. According to the Zynq UltraScale TRM [1], when transmit is disabled, the transmit buffer queue pointer resets to point to the address specified by the transmit buffer queue base address register. In the current implementation, the code merely resets `queue->tx_head` and `queue->tx_tail` to '0'. This approach presents several issues: - Packets already queued in the tx ring are silently lost, leading to memory leaks since the associated skbs cannot be released. - Concurrent write access to `queue->tx_head` and `queue->tx_tail` may occur from `macb_tx_poll()` or `macb_start_xmit()` when these values are reset to '0'. - The transmission may become stuck on a packet that has already been sent out, with its 'TX_USED' bit set, but has not yet been processed. However, due to the manipulation of 'queue->tx_head' and 'queue->tx_tail', `macb_tx_poll()` incorrectly assumes there are no packets to handle because `queue->tx_head == queue->tx_tail`. This issue is only resolved when a new packet is placed at this position. This is the root cause of the prolonged recovery time observed for the NFS root filesystem. To resolve this issue, shuffle the tx ring and tx skb array so that the first unsent packet is positioned at the start of the tx ring. Additionally, ensure that updates to `queue->tx_head` and `queue->tx_tail` are properly protected with the appropriate lock. [1] https://docs.amd.com/v/u/en-US/ug1085-zynq-ultrascale-trm
- Published
- May 8, 2026
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 5th percentile
- CWE
- CWE-401
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpAffected systems
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel6.1.165 and later · before 6.1.167
- linux linux kernel6.6.128 and later · before 6.6.130
- linux linux kernel6.12.75 and later · before 6.12.78
- linux linux kernel6.18.16 and later · before 6.18.20
- linux linux kernel6.19.6 and later · before 6.19.9
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
- d89b8b17057e16fad4564c71160e68ca549c1b42 and later · before c6783bfa31a59f34fe4feb1bdbf67791ef3fb0b7affected · git
- ec4445ae9e58aed88561d3d1dfa849b039c7782e and later · before 0a47c3889fcd843c72aa57fa8c4d06f5801fced4affected · git
- 6e704e89f16fd4a1145756210bc210f14f174f94 and later · before 88f974fe118cb4653f029929ecbca7cfe06132aeaffected · git
- 316d9fe71fb18bc9b1dba464fdb68dd201315eba and later · before 58f5d34f88e8f00910b692537f7b2efdb8c3705daffected · git
- b3a7aa33ca7d46be513fccf832d3540acfe587d0 and later · before 403182e0771b250cfde0fe7e1081d095ceaf8230affected · git
- bf9cf80cab81e39701861a42877a28295ade266f and later · before 881a0263d502e1a93ebc13a78254e9ad19520232affected · git
- 6.1.165 and later · before 6.1.167affected · semver
- 6.6.128 and later · before 6.6.130affected · semver
- 6.12.75 and later · before 6.12.78affected · semver
- 6.18.16 and later · before 6.18.20affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:14 | linux | before 6.19.10-1 | 6.19.10-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- 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
- CVE-2016-5195Race condition in mm/gup.c in the Linux kernel 2.x through 4.x before 4.8.3 allows local users to gain privileges by leveraging incorrect haKEV83Now
- CVE-2019-13272In the Linux kernel before 5.1.17, ptrace_link in kernel/ptrace.c mishandles the recording of the credentials of a process that wants to creKEV77This week
- CVE-2013-6282The (1) get_user and (2) put_user API functions in the Linux kernel before 3.5.5 on the v6k and v7 ARM platforms do not validate certain addKEV77This week
- CVE-2013-2094The perf_swevent_init function in kernel/events/core.c in the Linux kernel before 3.8.9 uses an incorrect integer data type, which allows loKEV77This week
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 | 0a47c3889fcd843c72aa57fa8c4d06f5801fced4 | Vendor (CNA) |
| Linux Linux | 403182e0771b250cfde0fe7e1081d095ceaf8230 | Vendor (CNA) |
| Linux Linux | 58f5d34f88e8f00910b692537f7b2efdb8c3705d | Vendor (CNA) |
| Linux Linux | 6.1.167 | Vendor (CNA) |
| Linux Linux | 6.12.78 | Vendor (CNA) |
| Linux Linux | 6.18.20 | Vendor (CNA) |
| Linux Linux | 6.19.9 | Vendor (CNA) |
| Linux Linux | 6.6.130 | Vendor (CNA) |
| Linux Linux | 881a0263d502e1a93ebc13a78254e9ad19520232 | Vendor (CNA) |
| Linux Linux | 88f974fe118cb4653f029929ecbca7cfe06132ae | Vendor (CNA) |
| Linux Linux | c6783bfa31a59f34fe4feb1bdbf67791ef3fb0b7 | Vendor (CNA) |
| debian:linux | 6.19.10-1 · Debian:14 | 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.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-0213 · May 12, 2026(Linux Kernel Güvenlik Bildirimi)
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)
CWE-401 · Missing Release of Memory after Effective LifetimeCVSS 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
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
- git.kernel.org/stable/c/0a47c3889fcd843c72aa57fa8c4d06f5801fced4
- git.kernel.org/stable/c/403182e0771b250cfde0fe7e1081d095ceaf8230
- git.kernel.org/stable/c/58f5d34f88e8f00910b692537f7b2efdb8c3705d
- git.kernel.org/stable/c/881a0263d502e1a93ebc13a78254e9ad19520232
- git.kernel.org/stable/c/88f974fe118cb4653f029929ecbca7cfe06132ae
- git.kernel.org/stable/c/c6783bfa31a59f34fe4feb1bdbf67791ef3fb0b7
Vendor advisories and official records. Exploit/PoC links are deliberately left out.