Bug 2305446 (CVE-2024-42301) - CVE-2024-42301 kernel: dev/parport: fix the array out-of-bounds risk
Summary: CVE-2024-42301 kernel: dev/parport: fix the array out-of-bounds risk
Keywords:
Status: NEW
Alias: CVE-2024-42301
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On: 2305781
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-08-17 09:22 UTC by OSIDB Bzimport
Modified: 2025-04-30 00:59 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2024:9635 0 None None None 2024-11-14 09:59:44 UTC
Red Hat Product Errata RHBA-2024:9811 0 None None None 2024-11-18 01:20:41 UTC
Red Hat Product Errata RHSA-2024:8856 0 None None None 2024-11-05 01:10:27 UTC
Red Hat Product Errata RHSA-2024:8870 0 None None None 2024-11-05 00:50:09 UTC
Red Hat Product Errata RHSA-2024:9315 0 None None None 2024-11-12 09:38:41 UTC
Red Hat Product Errata RHSA-2025:4342 0 None None None 2025-04-30 00:59:16 UTC

Description OSIDB Bzimport 2024-08-17 09:22:35 UTC
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]

Comment 1 errata-xmlrpc 2024-11-05 00:50:08 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8

Via RHSA-2024:8870 https://access.redhat.com/errata/RHSA-2024:8870

Comment 2 errata-xmlrpc 2024-11-05 01:10:26 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8

Via RHSA-2024:8856 https://access.redhat.com/errata/RHSA-2024:8856

Comment 3 errata-xmlrpc 2024-11-12 09:38:40 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9

Via RHSA-2024:9315 https://access.redhat.com/errata/RHSA-2024:9315

Comment 4 errata-xmlrpc 2025-04-30 00:59:15 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9.4 Extended Update Support

Via RHSA-2025:4342 https://access.redhat.com/errata/RHSA-2025:4342


Note You need to log in before you can comment on or make changes to this bug.