Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2023-53431: scsi: ses: Handle enclosure with just a primary component gracefully

Noroxi assessment

Priority: Monitor (action score 22/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.22% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 05143d90ac90b7abc6692285895a1ef460e008ee, 110d425cdfb15006f3c4fde5264e786a247b6b36, 176d7345b89ced72020a313bfa4e7f345d1c3aed.
  • Severity is disputed: the assigning authority (CNA) scores it 8.8, NVD 5.5.

Low priority for now. Upgrade to Linux Linux 05143d90ac90b7abc6692285895a1ef460e008ee, 110d425cdfb15006f3c4fde5264e786a247b6b36, 176d7345b89ced72020a313bfa4e7f345d1c3aed or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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 <dinghui@sangfor.com.cn>. 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 =====

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
Sep 18, 2025
Updated
Aug 5, 2026
EPSS
0.2% · 12th percentile
CWE
—

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
5.5
CNA · Linux
8.8
3.3 point gap

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

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2023-53431

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel2.6.25 and later · before 4.19.281
  • linux linux kernel4.20 and later · before 5.4.241
  • linux linux kernel5.5 and later · before 5.10.178
  • linux linux kernel5.11 and later · before 5.15.108
  • linux linux kernel5.16 and later · before 6.1.25
  • linux linux kernel6.2 and later · before 6.2.12
  • linux linux kernel6.3

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 2.6.25affected
    • 9927c68864e9c39cc317b4f559309ba29e642168 and later · before 4e7c498c3713b09bef20c76c7319555637e8bbd5affected · git
    • 9927c68864e9c39cc317b4f559309ba29e642168 and later · before 110d425cdfb15006f3c4fde5264e786a247b6b36affected · git
    • 9927c68864e9c39cc317b4f559309ba29e642168 and later · before 176d7345b89ced72020a313bfa4e7f345d1c3aedaffected · git
    • 9927c68864e9c39cc317b4f559309ba29e642168 and later · before 05143d90ac90b7abc6692285895a1ef460e008eeaffected · git
    • 9927c68864e9c39cc317b4f559309ba29e642168 and later · before f8e702c54413eee2d8f94f61d18adadac7c87e87affected · git
    • 9927c68864e9c39cc317b4f559309ba29e642168 and later · before eabc4872f172ecb8dd8536bc366a51868154a450affected · git
    • 9927c68864e9c39cc317b4f559309ba29e642168 and later · before c8e22b7a1694bb8d025ea636816472739d859145affected · git
    • before 2.6.25not affected · semver
    • 4.19.281 and later · up to and including 4.19.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.25-16.1.25-1
SUSE:Linux Enterprise Live Patching 12 SP5kernel-defaultbefore 4.12.14-122.283.14.12.14-122.283.1
SUSE:Linux Enterprise Live Patching 12 SP5kgraft-patch-SLE12-SP5_Update_75before 1-8.3.11-8.3.1
SUSE:Linux Enterprise Server 12 SP5-LTSSkernel-sourcebefore 4.12.14-122.283.14.12.14-122.283.1
SUSE:Linux Enterprise Server 12 SP5-LTSSkernel-symsbefore 4.12.14-122.283.14.12.14-122.283.1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2023-53428Sep 18, 2025 · powercap: arm_scmi: Remove recursion while parsing zones
    22Monitor
  • ← EarlierCVE-2023-53430Sep 18, 2025 · wifi: mt76: dma: fix memory leak running mt76_dma_tx_cleanup
    22Monitor
  • Later →CVE-2023-53432Sep 18, 2025 · firewire: net: fix use after free in fwnet_finish_incoming_packet()
    31Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux05143d90ac90b7abc6692285895a1ef460e008eeVendor (CNA)
Linux Linux110d425cdfb15006f3c4fde5264e786a247b6b36Vendor (CNA)
Linux Linux176d7345b89ced72020a313bfa4e7f345d1c3aedVendor (CNA)
Linux Linux4e7c498c3713b09bef20c76c7319555637e8bbd5Vendor (CNA)
Linux Linuxc8e22b7a1694bb8d025ea636816472739d859145Vendor (CNA)
Linux Linuxeabc4872f172ecb8dd8536bc366a51868154a450Vendor (CNA)
Linux Linuxf8e702c54413eee2d8f94f61d18adadac7c87e87Vendor (CNA)
debian:linux6.1.25-1 · Debian:12Package registry (OSV)
suse:kernel-default4.12.14-122.283.1 · SUSE:Linux Enterprise Live Patching 12 SP5Package registry (OSV)
suse:kernel-source4.12.14-122.283.1 · SUSE:Linux Enterprise Server 12 SP5-LTSSPackage registry (OSV)
suse:kernel-syms4.12.14-122.283.1 · SUSE:Linux Enterprise Server 12 SP5-LTSSPackage registry (OSV)
suse:kgraft-patch-SLE12-SP5_Update_751-8.3.1 · SUSE:Linux Enterprise Live Patching 12 SP5Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

Weakness class (CWE)

—

CVSS vector

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

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (6 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records