CVE-2023-53182

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • 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:

ACPICA: Avoid undefined behavior: applying zero offset to null pointer

ACPICA commit 770653e3ba67c30a629ca7d12e352d83c2541b1e

Before this change we see the following UBSAN stack trace in Fuchsia:

#0 0x000021e4213b3302 in acpi_ds_init_aml_walk(struct acpi_walk_state*, union acpi_parse_object*, struct acpi_namespace_node*, u8*, u32, struct acpi_evaluate_info*, u8) ../../third_party/acpica/source/components/dispatcher/dswstate.c:682 +0x233302 #1.2 0x000020d0f660777f in ubsan_get_stack_trace() compiler-rt/lib/ubsan/ubsan_diag.cpp:41 +0x3d77f #1.1 0x000020d0f660777f in maybe_print_stack_trace() compiler-rt/lib/ubsan/ubsan_diag.cpp:51 +0x3d77f #1 0x000020d0f660777f in ~scoped_report() compiler-rt/lib/ubsan/ubsan_diag.cpp:387 +0x3d77f #2 0x000020d0f660b96d in handlepointer_overflow_impl() compiler-rt/lib/ubsan/ubsan_handlers.cpp:809 +0x4196d #3 0x000020d0f660b50d in compiler-rt/lib/ubsan/ubsan_handlers.cpp:815 +0x4150d #4 0x000021e4213b3302 in acpi_ds_init_aml_walk(struct acpi_walk_state*, union acpi_parse_object*, struct acpi_namespace_node*, u8*, u32, struct acpi_evaluate_info*, u8) ../../third_party/acpica/source/components/dispatcher/dswstate.c:682 +0x233302 #5 0x000021e4213e2369 in acpi_ds_call_control_method(struct acpi_thread_state*, struct acpi_walk_state*, union acpi_parse_object*) ../../third_party/acpica/source/components/dispatcher/dsmethod.c:605 +0x262369 #6 0x000021e421437fac in acpi_ps_parse_aml(struct acpi_walk_state*) ../../third_party/acpica/source/components/parser/psparse.c:550 +0x2b7fac #7 0x000021e4214464d2 in acpi_ps_execute_method(struct acpi_evaluate_info*) ../../third_party/acpica/source/components/parser/psxface.c:244 +0x2c64d2 #8 0x000021e4213aa052 in acpi_ns_evaluate(struct acpi_evaluate_info*) ../../third_party/acpica/source/components/namespace/nseval.c:250 +0x22a052 #9 0x000021e421413dd8 in acpi_ns_init_one_device(acpi_handle, u32, void*, void**) ../../third_party/acpica/source/components/namespace/nsinit.c:735 +0x293dd8 #10 0x000021e421429e98 in acpi_ns_walk_namespace(acpi_object_type, acpi_handle, u32, u32, acpi_walk_callback, acpi_walk_callback, void*, void**) ../../third_party/acpica/source/components/namespace/nswalk.c:298 +0x2a9e98 #11 0x000021e4214131ac in acpi_ns_initialize_devices(u32) ../../third_party/acpica/source/components/namespace/nsinit.c:268 +0x2931ac #12 0x000021e42147c40d in acpi_initialize_objects(u32) ../../third_party/acpica/source/components/utilities/utxfinit.c:304 +0x2fc40d #13 0x000021e42126d603 in acpi::acpi_impl::initialize_acpi(acpi::acpi_impl*) ../../src/devices/board/lib/acpi/acpi-impl.cc:224 +0xed603

Add a simple check that avoids incrementing a pointer by zero, but otherwise behaves as before. Note that our findings are against ACPICA 20221020, but the same code exists on master.

CVSS v3
5.5
EG Score
5.5MEDIUMmedium confidence
EG Risk
29
EG Risk 29/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity55% × 45%
Exploitation0% × 40%
Automatability30% × 15%
CISA SSVC: Track at low or medium mission impact; Track or Attend at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.2%
EPSS %ILE
4th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track or Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 15, 2025

Last Modified

December 2, 2025

References (8)

Vendor Advisories for CVE-2023-53182(2)

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

Patch Availability(3)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatkernel-0:5.14.0-503.11.1.el9_52024-11-12redhat
redhatkernel-0:4.18.0-553.el8_102024-05-22redhat
linuxKernel @ 4.14.316 (fixes >=2.6.12)—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 (33 versions)
  • every version up to 5.10.191-1: fixed in 5.10.191-1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.27-1
  • every version up to 6.1.37-1: fixed in 6.1.37-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.3.7-1: fixed in 6.3.7-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.3.7-1: fixed in 6.3.7-1
—

Data Freshness Timeline

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

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

Showing the most recent 100 of 167 total refreshes for this CVE.

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

Related CVEs(same vendor)

Frequently asked(5)

What is CVE-2023-53182?
CVE-2023-53182 is a medium vulnerability published on September 15, 2025. In the Linux kernel, the following vulnerability has been resolved: ACPICA: Avoid undefined behavior: applying zero offset to null pointer ACPICA commit 770653e3ba67c30a629ca7d12e352d83c2541b1e Before this change we see the following UBSAN stack trace in Fuchsia: #0 0x000021e4213b3302 in…
When was CVE-2023-53182 disclosed?
CVE-2023-53182 was first published on September 15, 2025, with the most recent update on December 2, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2023-53182 actively exploited?
CVE-2023-53182 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (4th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2023-53182?
CVE-2023-53182 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2023-53182?
A fix for CVE-2023-53182 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2023-53182 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-53182

Explore →

Is Your Infrastructure Affected by CVE-2023-53182?

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

Book a Demo →Browse All CVEs