CVE-2023-53431

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score 5.5 from GitHub Security Advisory published 2025-09-18. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3

Also known asEUVD-2025-29874 (ENISA EUVD) · GHSA-36rm-q238-p59m (GitHub Security Advisories)Source: ENISA EUVD

5.5EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 5.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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 .

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 =====

CVSS v3
5.5
EG Score
5.5MEDIUMmedium confidence
EG Risk
25
EG Risk 25/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity55% × 45%
Impact severity (EG Severity): CVSS 5.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
12th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (5.5): severity, escalated by confirmed exploitation. This CVE's 5.5 is its impact severity (EG Severity), not escalated.

EG Severity
5.5 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-25). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

September 18, 2025

Last Modified

August 5, 2026

References (7)

Vendor Advisories for CVE-2023-53431(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(2)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatkernel-0:5.14.0-362.8.1.el9_32023-11-07redhat
linuxKernel @ 4.19.281 (fixes >=2.6.25)—osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
linux5.10.103-1 ... 5.10.92-2 (25 versions)
  • every version up to 5.10.178-1: fixed in 5.10.178-1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.1.25-1: fixed in 6.1.25-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.1.25-1: fixed in 6.1.25-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.1.25-1: fixed in 6.1.25-1
—

Data Freshness Timeline

(refreshed 7× in last 7d / 37× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 93 of 199 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 7 repeat rows among the latest 100 are merged into the row they repeat. The 106 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-02 16:40 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  2. 2026-11-01 16:31 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  3. 2026-10-31 16:30 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  4. 2026-10-30 16:31 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  5. 2026-10-29 16:30 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  6. 2026-10-28 16:29 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  7. 2026-10-27 16:29 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  8. 2026-10-26 16:29 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  9. 2026-10-25 17:28 UTCEG score recompute
  10. 2026-10-25 16:30 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  11. 2026-10-24 16:29 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  12. 2026-10-24 11:35 UTCEG score recompute
  13. 2026-10-24 11:35 UTCGHSA enrichmentGHSA-36rm-q238-p59m · GitHub CVSS 5.5
  14. 2026-10-23 16:29 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  15. 2026-10-22 16:31 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  16. 2026-10-21 16:29 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  17. 2026-10-20 16:30 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  18. 2026-10-19 16:29 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  19. 2026-10-19 14:25 UTCOSV refresh
  20. 2026-10-18 16:29 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  21. 2026-10-18 07:40 UTCEG score recompute
  22. 2026-10-17 16:30 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  23. 2026-10-16 16:36 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  24. 2026-10-15 16:29 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  25. 2026-10-14 16:30 UTCEPSS rescoreEPSS 0.2% · 11th percentile
Show 68 more
  1. 2026-10-13 16:30 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  2. 2026-10-12 18:12 UTCEG score recompute
  3. 2026-10-12 16:31 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  4. 2026-10-11 21:37 UTCEG score recompute
  5. 2026-10-11 13:45 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  6. 2026-10-10 19:58 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  7. 2026-10-09 20:05 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  8. 2026-10-08 17:06 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  9. 2026-10-07 23:46 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  10. 2026-10-06 15:15 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  11. 2026-10-05 17:41 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  12. 2026-10-04 23:20 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  13. 2026-10-03 14:23 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  14. 2026-10-01 19:48 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  15. 2026-09-30 16:37 UTCEG score recompute
  16. 2026-09-30 15:01 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  17. 2026-09-29 15:17 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  18. 2026-09-28 13:49 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  19. 2026-09-26 20:33 UTCOSV refresh
  20. 2026-09-26 00:22 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  21. 2026-09-24 14:01 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  22. 2026-09-23 13:46 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  23. 2026-09-20 20:14 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  24. 2026-09-18 19:26 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  25. 2026-09-16 14:06 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  26. 2026-09-16 05:11 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  27. 2026-09-15 03:08 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  28. 2026-09-13 16:45 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  29. 2026-09-12 14:58 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  30. 2026-09-11 14:51 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  31. 2026-09-11 09:34 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  32. 2026-09-08 21:58 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  33. 2026-09-07 15:59 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  34. 2026-09-07 06:18 UTCOSV refresh
  35. 2026-09-06 13:46 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  36. 2026-09-05 15:26 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  37. 2026-09-04 13:58 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  38. 2026-09-04 05:04 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  39. 2026-09-02 14:10 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  40. 2026-09-01 13:52 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  41. 2026-09-01 04:36 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  42. 2026-08-30 19:15 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  43. 2026-08-30 01:20 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  44. 2026-08-28 21:39 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  45. 2026-08-27 14:23 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  46. 2026-08-26 14:44 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  47. 2026-08-25 13:47 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  48. 2026-08-23 00:17 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  49. 2026-08-21 23:47 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  50. 2026-08-20 22:53 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  51. 2026-08-20 16:01 UTCOSV refresh
  52. 2026-08-19 17:02 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  53. 2026-08-18 13:46 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  54. 2026-08-16 14:54 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  55. 2026-08-16 02:12 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  56. 2026-08-15 01:28 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  57. 2026-08-13 21:58 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  58. 2026-08-12 13:49 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  59. 2026-08-11 13:40 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  60. 2026-08-10 23:58 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  61. 2026-08-09 13:44 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  62. 2026-08-08 16:35 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  63. 2026-08-07 16:25 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  64. 2026-08-06 13:45 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  65. 2026-08-05 19:15 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  66. 2026-08-05 10:19 UTCEG score recompute
  67. 2026-08-05 10:19 UTCGHSA enrichmentGHSA-36rm-q238-p59m · GitHub CVSS 5.5
  68. 2026-08-04 10:58 UTCEG score recompute

Related CVEs(same vendor)

Frequently asked(5)

What is CVE-2023-53431?
CVE-2023-53431 is a medium-severity vulnerability; its CVE record was published on September 18, 2025. 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…
When was the CVE record for CVE-2023-53431 published?
The CVE record for CVE-2023-53431 was published on September 18, 2025. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of August 5, 2026; the record at its source may have been updated since.
Is CVE-2023-53431 actively exploited?
CVE-2023-53431 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (12th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2023-53431?
CVE-2023-53431 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2023-53431?
A fix for CVE-2023-53431 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2023-53431 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2023-53431

Explore →

Is Your Infrastructure Affected by CVE-2023-53431?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs