CVE-2023-53535: net: bcmgenet: Add a check for oversized packets
In the Linux kernel, the following vulnerability has been resolved:
net: bcmgenet: Add a check for oversized packets
Occasionnaly we may get oversized packets from the hardware which
exceed the nomimal 2KiB buffer size we allocate SKBs with. Add an early
check which drops the packet to avoid invoking skb_over_panic() and move
on to processing the next packet.
Security readout for executives and security teams
Plain-English summary
This Linux kernel issue can cause systems with the Broadcom GENET network driver to mishandle oversized packets from hardware and hit a kernel panic path. The likely business impact is availability loss, not confirmed data theft. Public sources do not provide CVSS, CWE, or confirmed exploitation.
Executive priority
Treat as a targeted availability risk for Linux-based devices using Broadcom GENET Ethernet. Prioritize patching where those devices support critical network services, but do not assume broad enterprise exposure without driver and hardware confirmation.
Technical view
The bcmgenet receive path could receive packets larger than the nominal 2 KiB SKB allocation. The fix adds an early oversized-packet check and drops those packets before skb_over_panic() can be triggered. Affected exposure depends on running affected Linux kernel versions with the bcmgenet driver and matching hardware.
Likely exposure
Exposure is likely limited to Linux systems that use the bcmgenet Broadcom GENET Ethernet driver on affected kernel versions. General Linux systems without this driver or hardware are unlikely to be exposed based on the provided sources.
Exploitation context
The source bundle does not show CISA KEV listing, active exploitation, public exploit details, or a CVSS score. The described failure mode suggests potential denial of service through kernel panic, but exploitability conditions are not fully documented.
Researcher notes
Evidence is strongest for the code defect and fix intent, not for attacker prerequisites. The CVE record lists Linux kernel affected versions and multiple stable commit references, but provides no CVSS, CWE, exploit status, or detailed attack scenario.
Mitigation direction
Apply a kernel or distribution update containing the referenced stable bcmgenet fixes.
Check your Linux vendor advisory for supported fixed package versions.
Prioritize devices that load the bcmgenet driver or depend on Broadcom GENET Ethernet.
If patching is delayed, monitor affected devices for kernel panic or network receive errors.
Validation and detection
Inventory kernels and identify systems using the bcmgenet driver.
Compare deployed kernel builds against vendor-fixed versions or referenced stable commits.
Review kernel logs for skb_over_panic or bcmgenet receive-path crash evidence.
Confirm updates through normal reboot and kernel version verification processes.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2023-53535 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
0CVSS vectors
3Timeline events
0ADP providers
9Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
Oct 4, 2025, 15:16 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.