net: lantiq: fix memory corruption in RX ring
In the Linux kernel, the following vulnerability has been resolved: net: lantiq: fix memory corruption in RX ring In a situation where memory allocation or dma mapping fails, an invalid address is programmed into the descriptor. This can lead to memory corruption. If the memory allocation fails, DMA should reuse the previous skb and mapping and drop the packet. This patch also increments rx drop counter.
- Published
- Mar 25, 2024
- Updated
- Aug 5, 2026
- EPSS
- 0.6% · 46th percentile
- CWE
- CWE-770
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
39
Monitor
Low priority for now.
- CVSS
- 39 / 40 · 9.8 / 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
- —
- CNA · Linux
- 9.8
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Affected 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 kernel4.20 and later · before 5.4.124
- linux linux kernel5.5 and later · before 5.10.42
- linux linux kernel5.11 and later · before 5.12.9
- linux linux kernel5.13
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.20affected
- fe1a56420cf2ec28c8eceef672b87de0bbe1a260 and later · before 8bb1077448d43a871ed667520763e3b9f9b7975daffected · git
- fe1a56420cf2ec28c8eceef672b87de0bbe1a260 and later · before 5ac72351655f8b033a2935646f53b7465c903418affected · git
- fe1a56420cf2ec28c8eceef672b87de0bbe1a260 and later · before 46dd4abced3cb2c912916f4a5353e0927db0c4a2affected · git
- fe1a56420cf2ec28c8eceef672b87de0bbe1a260 and later · before c7718ee96dbc2f9c5fc3b578abdf296dd44b9c20affected · git
- before 4.20not affected · semver
- 5.4.124 and later · up to and including 5.4.*not affected · semver
- 5.10.42 and later · up to and including 5.10.*not affected · semver
- 5.12.9 and later · up to and including 5.12.*not affected · semver
- 5.13 and laternot affected · original_commit_for_fix
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 5.14.6-1 | 5.14.6-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 | 46dd4abced3cb2c912916f4a5353e0927db0c4a2 | Vendor (CNA) |
| Linux Linux | 5ac72351655f8b033a2935646f53b7465c903418 | Vendor (CNA) |
| Linux Linux | 8bb1077448d43a871ed667520763e3b9f9b7975d | Vendor (CNA) |
| Linux Linux | c7718ee96dbc2f9c5fc3b578abdf296dd44b9c20 | Vendor (CNA) |
| Debian:linux | 5.14.6-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.
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.
- CVE-2024-3596956 days apartipv6: fix race condition between ipv6_get_ifaddr and ipv6_del_addr35Monitor
- CVE-2021-4755160 days apartdrm/amd/amdkfd: Fix kernel panic when reset failed and been triggered again31Monitor
- CVE-2024-3402791 days apartf2fs: compress: fix to cover {reserve,release}_compress_blocks() w/ cp_rwsem lock31Monitor
- CVE-2021-4713010 days apartnvmet: fix freeing unallocated p2pmem30Monitor
- CVE-2023-5252923 days apartHID: sony: Fix a potential memory leak in sony_probe()24Monitor
- CVE-2024-2689423 days apartACPI: processor_idle: Fix memory leak in acpi_processor_power_exit()24Monitor
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).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-770 · Allocation of Resources Without Limits or ThrottlingCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- FloodingCAPEC-125likelihood: High · Medium
- Excessive AllocationCAPEC-130likelihood: Medium · Medium
- XML Ping of the DeathCAPEC-147likelihood: Low · Medium
- Exponential Data ExpansionCAPEC-197likelihood: High · Medium
- Serialized Data Parameter BlowupCAPEC-229likelihood: High · High
- Serialized Data with Nested PayloadsCAPEC-230likelihood: Medium · High
- Oversized Serialized Data PayloadsCAPEC-231likelihood: Medium · High
- HTTP DoSCAPEC-469Low
ATT&CK techniques
- Network Denial of Service:Direct Network FloodT1498.001
- Network Denial of Service:Reflection AmplificationT1498.002
- Endpoint Denial of ServiceT1499
- Endpoint Denial of Service: OS Exhaustion FloodT1499.001
- Endpoint Denial of Service:Service Exhaustion FloodT1499.002
- Endpoint Denial of Service:Application Exhaustion FloodT1499.003
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for all 385,000+ vulnerabilities; 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 helpChange log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
- git.kernel.org/stable/c/46dd4abced3cb2c912916f4a5353e0927db0c4a2
- git.kernel.org/stable/c/5ac72351655f8b033a2935646f53b7465c903418
- git.kernel.org/stable/c/8bb1077448d43a871ed667520763e3b9f9b7975d
- git.kernel.org/stable/c/c7718ee96dbc2f9c5fc3b578abdf296dd44b9c20
Vendor advisories and official records. Exploit/PoC links are deliberately left out.