CVE-2024-42301: dev/parport: fix the array out-of-bounds risk
In the Linux kernel, the following vulnerability has been resolved:
dev/parport: fix the array out-of-bounds risk
Fixed array out-of-bounds issues caused by sprintf
by replacing it with snprintf for safer data copying,
ensuring the destination buffer is not overflowed.
Below is the stack trace I encountered during the actual issue:
[ 66.575408s] [pid:5118,cpu4,QThread,4]Kernel panic - not syncing: stack-protector:
Kernel stack is corrupted in: do_hardware_base_addr+0xcc/0xd0 [parport]
[ 66.575408s] [pid:5118,cpu4,QThread,5]CPU: 4 PID: 5118 Comm:
QThread Tainted: G S W O 5.10.97-arm64-desktop #7100.57021.2
[ 66.575439s] [pid:5118,cpu4,QThread,6]TGID: 5087 Comm: EFileApp
[ 66.575439s] [pid:5118,cpu4,QThread,7]Hardware name: HUAWEI HUAWEI QingYun
PGUX-W515x-B081/SP1PANGUXM, BIOS 1.00.07 04/29/2024
[ 66.575439s] [pid:5118,cpu4,QThread,8]Call trace:
[ 66.575469s] [pid:5118,cpu4,QThread,9] dump_backtrace+0x0/0x1c0
[ 66.575469s] [pid:5118,cpu4,QThread,0] show_stack+0x14/0x20
[ 66.575469s] [pid:5118,cpu4,QThread,1] dump_stack+0xd4/0x10c
[ 66.575500s] [pid:5118,cpu4,QThread,2] panic+0x1d8/0x3bc
[ 66.575500s] [pid:5118,cpu4,QThread,3] __stack_chk_fail+0x2c/0x38
[ 66.575500s] [pid:5118,cpu4,QThread,4] do_hardware_base_addr+0xcc/0xd0 [parport]
Security readout for executives and security teams
Plain-English summary
A bounds error in the Linux parallel-port subsystem can corrupt kernel memory and crash the operating system. The supplied assessment rates potential confidentiality, integrity, and availability impact as high, but the documented real-world outcome is a kernel panic rather than confirmed code execution.
Executive priority
Treat this as a high-priority kernel maintenance issue for exposed multi-user Linux systems. Accelerate normal patching where local untrusted access exists; otherwise schedule the supported kernel update promptly. There is no supplied evidence supporting an emergency response for active exploitation.
Technical view
The Linux parport code used sprintf for data copying in a path associated with do_hardware_base_addr. Unbounded output could exceed the destination array, corrupt the kernel stack, and trigger a stack-protector panic. Stable-kernel changes replace sprintf with snprintf to constrain the write.
Likely exposure
Exposure is most likely on systems running an affected Linux kernel where the parport component is present and reachable by a local, low-privileged user. The bundle lists affected kernel versions, but does not provide reliable distribution-package mappings or configuration prerequisites.
Exploitation context
The vulnerability requires local access according to CVSS and does not require user interaction. The bundle marks it absent from KEV and provides no evidence of active exploitation. It documents an encountered kernel panic, not confirmed attacker-controlled code execution.
Researcher notes
The bundle provides multiple stable-branch commits but an ambiguous affected-version list, including repeated commit identifiers. It does not establish exact triggering prerequisites, public proof-of-concept availability, or successful privilege escalation. The observed evidence supports stack corruption and denial of service; broader impact is represented by the supplied CVSS vector.
Mitigation direction
Install the distribution-supported kernel update that incorporates the relevant stable-kernel fix.
Reboot into the updated kernel after installation.
Consult Linux distribution advisories to confirm the fixed package version for each maintained branch.
Prioritize multi-user systems where untrusted users can obtain local accounts.
Validation and detection
Record each system's running kernel version and distribution package release.
Confirm the installed package includes the applicable upstream stable commit or vendor backport.
Verify systems rebooted into the corrected kernel rather than retaining an older running kernel.
Determine whether the parport component is enabled or used on potentially affected hosts.
Review kernel logs for stack-protector failures or panics involving do_hardware_base_addr and parport.
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-2024-42301 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.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.