Linux Kernel up to 6.5.2 scsi qla4xxx_set_chap_entry privilege escalation

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
5.4$0-$5k0.00

Summaryinfo

A vulnerability classified as problematic has been found in Linux Kernel up to 6.5.2. Affected by this issue is the function qla4xxx_set_chap_entry of the component scsi. The manipulation leads to an unknown weakness. This vulnerability is documented as CVE-2023-53456. There is not any exploit available. It is recommended to upgrade the affected component.

Detailsinfo

A vulnerability was found in Linux Kernel up to 6.5.2. It has been rated as problematic. This issue affects the function qla4xxx_set_chap_entry of the component scsi. The impact remains unknown. The summary by CVE is:

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.

It is possible to read the advisory at git.kernel.org. The identification of this vulnerability is CVE-2023-53456 since 09/17/2025. Technical details of the vulnerability are known, but there is no available exploit. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 01/17/2026).

The vulnerability scanner Nessus provides a plugin with the ID 269618 (Linux Distros Unpatched Vulnerability : CVE-2023-53456), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 4.14.326, 4.19.295, 5.4.257, 5.10.195, 5.15.132, 6.1.53, 6.4.16 or 6.5.3 eliminates this vulnerability. Applying the patch cfa6a1a79ed6d336fac7a5d87eb5471e4401829f/5925e224cc6edfef57b20447f18323208461309b/47f3be62eab50b8cd7e1ae5fc2c4dae687497c34/6d65079c69dc1feb817ed71f5bd15e83a7d6832d/f61fc650c47849637fa1771a31a11674c824138a/25feffb3fbd51ae81d92c65cebc0e932663828b3/4ed21975311247bb84e82298eeb359ec0a0fa84d/b018c0440b871d8b001c996e95fa4538bd292de6/47cd3770e31df942e2bb925a9a855c79ed0662eb is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.

The vulnerability is also documented in the databases at Tenable (269618), EUVD (EUVD-2025-32799) and CERT Bund (WID-SEC-2025-2187). Be aware that VulDB is the high quality source for vulnerability data.

Affected

  • Amazon Linux 2
  • Red Hat Enterprise Linux
  • SUSE Linux
  • Oracle Linux
  • Open Source Linux Kernel
  • Dell Secure Connect Gateway

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.5
VulDB Meta Temp Score: 5.4

VulDB Base Score: 5.5
VulDB Temp Score: 5.3
VulDB Vector: 🔒
VulDB Reliability: 🔍

NVD Base Score: 5.5
NVD Vector: 🔒

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Privilege escalation
CWE: Unknown
CAPEC: 🔒
ATT&CK: 🔒

Physical: Partially
Local: Yes
Remote: Partially

Availability: 🔒
Status: Not defined

EPSS Score: 🔒
EPSS Percentile: 🔒

Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 269618
Nessus Name: Linux Distros Unpatched Vulnerability : CVE-2023-53456

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Kernel 4.14.326/4.19.295/5.4.257/5.10.195/5.15.132/6.1.53/6.4.16/6.5.3
Patch: cfa6a1a79ed6d336fac7a5d87eb5471e4401829f/5925e224cc6edfef57b20447f18323208461309b/47f3be62eab50b8cd7e1ae5fc2c4dae687497c34/6d65079c69dc1feb817ed71f5bd15e83a7d6832d/f61fc650c47849637fa1771a31a11674c824138a/25feffb3fbd51ae81d92c65cebc0e932663828b3/4ed21975311247bb84e82298eeb359ec0a0fa84d/b018c0440b871d8b001c996e95fa4538bd292de6/47cd3770e31df942e2bb925a9a855c79ed0662eb

Timelineinfo

09/17/2025 CVE reserved
10/01/2025 +14 days Advisory disclosed
10/01/2025 +0 days VulDB entry created
01/17/2026 +108 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2023-53456 (🔒)
GCVE (CVE): GCVE-0-2023-53456
GCVE (VulDB): GCVE-100-326591
EUVD: 🔒
CERT Bund: WID-SEC-2025-2187 - Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service

Entryinfo

Created: 10/01/2025 15:04
Updated: 01/17/2026 21:21
Changes: 10/01/2025 15:04 (57), 10/12/2025 01:08 (2), 11/24/2025 03:51 (7), 01/17/2026 01:28 (10), 01/17/2026 21:21 (1)
Complete: 🔍
Cache ID: 216::103

Be aware that VulDB is the high quality source for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you need the next level of professionalism?

Upgrade your account now!