CVE-2023-53456
Unknown Unknown - Not Provided
BaseFortify

Publication date: 2025-10-01

Last updated on: 2025-10-02

Assigner: kernel.org

Description
In the Linux kernel, the following vulnerability has been resolved: scsi: qla4xxx: Add length check when parsing nlattrs There are three places that qla4xxx parses nlattrs: - qla4xxx_set_chap_entry() - qla4xxx_iface_set_param() - qla4xxx_sysfs_ddb_set_param() and each of them directly converts the nlattr to specific pointer of structure without length checking. This could be dangerous as those attributes are not validated and a malformed nlattr (e.g., length 0) could result in an OOB read that leaks heap dirty data. Add the nla_len check before accessing the nlattr data and return EINVAL if the length check fails.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2025-10-01
Last Modified
2025-10-02
Generated
2026-05-07
AI Q&A
2025-10-01
EPSS Evaluated
2026-05-05
NVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
linux linux_kernel From 5.15.160 (inc) to 5.16 (inc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

This vulnerability exists in the Linux kernel's qla4xxx driver where it parses netlink attributes (nlattrs) without checking their length. Specifically, three functions (qla4xxx_set_chap_entry, qla4xxx_iface_set_param, and qla4xxx_sysfs_ddb_set_param) convert nlattrs directly to pointers without validating their size. If a malformed nlattr with an invalid length (e.g., length 0) is processed, it can cause an out-of-bounds (OOB) read, potentially leaking heap memory data. The fix involves adding length checks before accessing nlattr data and returning an error if the check fails.


How can this vulnerability impact me? :

This vulnerability can lead to an out-of-bounds read in the Linux kernel's qla4xxx driver, which may cause leakage of heap memory data. Such data leakage could expose sensitive information from kernel memory, potentially compromising system security and privacy.


What immediate steps should I take to mitigate this vulnerability?

The immediate step to mitigate this vulnerability is to update the Linux kernel to a version where the qla4xxx driver includes the length check for nlattrs parsing. This fix adds nla_len checks before accessing nlattr data and returns an error if the length check fails, preventing out-of-bounds reads.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart