SECUFOCUSNOW
Home›CVE index›CVE-2024-42301
Review reviewHigh

CVE-2024-42301

Linux Linux, linux kernel

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-deskto...

CVSS
7.8
EPSS
0.23%
14.4% percentile
CISA KEV
Not listed
Published
2024.08.17
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability0.23%
Technical severityCVSS 7.8

Vulnerability overview

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-deskto...

Affected product and versions

Product
Linux Linux, linux kernel
Affected versions
>= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 166a0bddcc27de41fe13f861c8348e8e53e988c8, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 47b3dce100778001cd76f7e9188944b5cb27a76d, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < a44f88f7576bc1916d8d6293f5c62fbe7cbe03e0, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < c719b393374d3763e64900ee19aaed767d5a08d6, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 7f4da759092a1a6ce35fb085182d02de8cc4cc84, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < b579ea3516c371ecf59d073772bc45dfd28c8a0e, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 7789a1d6792af410aa9b39a1eb237ed24fa2170a, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < ab11dac93d2d568d151b1918d7b84c2d02bacbd5, >= 2.6.12, < 4.19.320, >= 4.20 < 5.4.282, >= 5.5 < 5.10.224, >= 5.11 < 5.15.165, >= 5.16 < 6.1.103, >= 6.2 < 6.6.44, >= 6.7 < 6.10.3
Fixed versions
4.19.320, 5.4.282, 5.10.224, 5.15.165, 6.1.103, 6.6.44, 6.10.3

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that Linux Linux, linux kernel and an affected version are present.

  2. 2
    Prioritize

    Combine exploitation signals with asset exposure and business criticality.

  3. 3
    Remediate

    Follow the vendor advisory or supported update path and preserve rollback options.

  4. 4
    Verify

    Recheck the version, service health, access paths, and relevant logs.

Technical data

CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CWE
CWE-129