Linux Kernel up to 6.2.2 scsi 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 was found in Linux Kernel up to 6.2.2. It has been classified as critical. The impacted element is an unknown function of the component scsi. Performing a manipulation results in an unknown weakness. This vulnerability was named CVE-2023-53431. There is no available exploit. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability, which was classified as critical, was found in Linux Kernel up to 6.2.2. This affects an unknown code block of the component scsi. The impact remains unknown. The summary by CVE is:

In the Linux kernel, the following vulnerability has been resolved: scsi: ses: Handle enclosure with just a primary component gracefully This reverts commit 3fe97ff3d949 ("scsi: ses: Don't attach if enclosure has no components") and introduces proper handling of case where there are no detected secondary components, but primary component (enumerated in num_enclosures) does exist. That fix was originally proposed by Ding Hui <[email protected]>. Completely ignoring devices that have one primary enclosure and no secondary one results in ses_intf_add() bailing completely scsi 2:0:0:254: enclosure has no enumerated components scsi 2:0:0:254: Failed to bind enclosure -12ven in valid configurations such even on valid configurations with 1 primary and 0 secondary enclosures as below: # sg_ses /dev/sg0 3PARdata SES 3321 Supported diagnostic pages: Supported Diagnostic Pages [sdp] [0x0] Configuration (SES) [cf] [0x1] Short Enclosure Status (SES) [ses] [0x8] # sg_ses -p cf /dev/sg0 3PARdata SES 3321 Configuration diagnostic page: number of secondary subenclosures: 0 generation code: 0x0 enclosure descriptor list Subenclosure identifier: 0 [primary] relative ES process id: 0, number of ES processes: 1 number of type descriptor headers: 1 enclosure logical identifier (hex): 20000002ac02068d enclosure vendor: 3PARdata product: VV rev: 3321 type descriptor header and text list Element type: Unspecified, subenclosure id: 0 number of possible elements: 1 The changelog for the original fix follows ===== We can get a crash when disconnecting the iSCSI session, the call trace like this: [ffff00002a00fb70] kfree at ffff00000830e224 [ffff00002a00fba0] ses_intf_remove at ffff000001f200e4 [ffff00002a00fbd0] device_del at ffff0000086b6a98 [ffff00002a00fc50] device_unregister at ffff0000086b6d58 [ffff00002a00fc70] __scsi_remove_device at ffff00000870608c [ffff00002a00fca0] scsi_remove_device at ffff000008706134 [ffff00002a00fcc0] __scsi_remove_target at ffff0000087062e4 [ffff00002a00fd10] scsi_remove_target at ffff0000087064c0 [ffff00002a00fd70] __iscsi_unbind_session at ffff000001c872c4 [ffff00002a00fdb0] process_one_work at ffff00000810f35c [ffff00002a00fe00] worker_thread at ffff00000810f648 [ffff00002a00fe70] kthread at ffff000008116e98 In ses_intf_add, components count could be 0, and kcalloc 0 size scomp, but not saved in edev->component[i].scratch In this situation, edev->component[0].scratch is an invalid pointer, when kfree it in ses_intf_remove_enclosure, a crash like above would happen The call trace also could be other random cases when kfree cannot catch the invalid pointer We should not use edev->component[] array when the components count is 0 We also need check index when use edev->component[] array in ses_enclosure_data_process =====

It is possible to read the advisory at git.kernel.org. This vulnerability is uniquely identified as CVE-2023-53431 since 09/17/2025. The technical details are unknown and an exploit is not publicly available. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 12/12/2025).

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

Upgrading to version 4.14.308, 4.19.276, 5.4.235, 5.10.173, 5.15.99, 6.1.16 or 6.2.3 eliminates this vulnerability. Applying the patch 4863fefc8a8cc8e8f6c7635b12d9dffaa0a12d86/feefd5232ecb788f0666f75893a7a86faec8bbcc/6069e04a922a0488bcf4f1017d38d18afda8194c/d68937dfc73ee7f61cf3424fa3225be93cacaa00/6fce2307650a190e343a84537c278d499fa37c26/5ca5470b33e5221dd3e5be81108697c22dd38b56/f182ad02024d3f45374a9e0c9d76f28b776d762d/3fe97ff3d94934649abb0652028dd7296170c8d0 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 (265518) and CERT Bund (WID-SEC-2025-2092). Be aware that VulDB is the high quality source for vulnerability data.

Affected

  • Amazon Linux 2
  • Red Hat Enterprise Linux
  • SUSE Linux
  • Oracle Linux
  • SUSE openSUSE
  • RESF Rocky Linux
  • Open Source Linux Kernel
  • Dell Secure Connect Gateway
  • IBM QRadar SIEM

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: 265518
Nessus Name: Linux Distros Unpatched Vulnerability : CVE-2023-53431

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Kernel 4.14.308/4.19.276/5.4.235/5.10.173/5.15.99/6.1.16/6.2.3
Patch: 4863fefc8a8cc8e8f6c7635b12d9dffaa0a12d86/feefd5232ecb788f0666f75893a7a86faec8bbcc/6069e04a922a0488bcf4f1017d38d18afda8194c/d68937dfc73ee7f61cf3424fa3225be93cacaa00/6fce2307650a190e343a84537c278d499fa37c26/5ca5470b33e5221dd3e5be81108697c22dd38b56/f182ad02024d3f45374a9e0c9d76f28b776d762d/3fe97ff3d94934649abb0652028dd7296170c8d0

Timelineinfo

09/17/2025 CVE reserved
09/18/2025 +1 days Advisory disclosed
09/18/2025 +0 days VulDB entry created
12/12/2025 +85 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2023-53431 (🔒)
GCVE (CVE): GCVE-0-2023-53431
GCVE (VulDB): GCVE-100-324903
CERT Bund: WID-SEC-2025-2092 - Linux Kernel: Mehrere Schwachstellen erm&ouml;glichen Denial of Service

Entryinfo

Created: 09/18/2025 19:16
Updated: 12/12/2025 01:00
Changes: 09/18/2025 19:16 (57), 09/20/2025 20:01 (7), 09/22/2025 05:43 (2), 11/29/2025 18:41 (1), 12/12/2025 01:00 (11)
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.

Are you interested in using VulDB?

Download the whitepaper to learn more about our service!