CVE-2023-53742

UNRATEDCVSS · not yet scored
—
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No CVSS published and no exploitation signals yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS v2: —Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

In the Linux kernel, the following vulnerability has been resolved:

kcsan: Avoid READ_ONCE() in read_instrumented_memory()

Haibo Li reported:

| Unable to handle kernel paging request at virtual address | ffffff802a0d8d7171 | Mem abort info:o: | ESR = 0x9600002121 | EC = 0x25: DABT (current EL), IL = 32 bitsts | SET = 0, FnV = 0 0 | EA = 0, S1PTW = 0 0 | FSC = 0x21: alignment fault | Data abort info:o: | ISV = 0, ISS = 0x0000002121 | CM = 0, WnR = 0 0 | swapper pgtable: 4k pages, 39-bit VAs, pgdp=000000002835200000 | [ffffff802a0d8d71] pgd=180000005fbf9003, p4d=180000005fbf9003, | pud=180000005fbf9003, pmd=180000005fbe8003, pte=006800002a0d8707 | Internal error: Oops: 96000021 [#1] PREEMPT SMP | Modules linked in: | CPU: 2 PID: 45 Comm: kworker/u8:2 Not tainted | 5.15.78-android13-8-g63561175bbda-dirty #1 | ... | pc : kcsan_setup_watchpoint+0x26c/0x6bc | lr : kcsan_setup_watchpoint+0x88/0x6bc | sp : ffffffc00ab4b7f0 | x29: ffffffc00ab4b800 x28: ffffff80294fe588 x27: 0000000000000001 | x26: 0000000000000019 x25: 0000000000000001 x24: ffffff80294fdb80 | x23: 0000000000000000 x22: ffffffc00a70fb68 x21: ffffff802a0d8d71 | x20: 0000000000000002 x19: 0000000000000000 x18: ffffffc00a9bd060 | x17: 0000000000000001 x16: 0000000000000000 x15: ffffffc00a59f000 | x14: 0000000000000001 x13: 0000000000000000 x12: ffffffc00a70faa0 | x11: 00000000aaaaaaab x10: 0000000000000054 x9 : ffffffc00839adf8 | x8 : ffffffc009b4cf00 x7 : 0000000000000000 x6 : 0000000000000007 | x5 : 0000000000000000 x4 : 0000000000000000 x3 : ffffffc00a70fb70 | x2 : 0005ff802a0d8d71 x1 : 0000000000000000 x0 : 0000000000000000 | Call trace: | kcsan_setup_watchpoint+0x26c/0x6bc | __tsan_read2+0x1f0/0x234 | inflate_fast+0x498/0x750 | zlib_inflate+0x1304/0x2384 | __gunzip+0x3a0/0x45c | gunzip+0x20/0x30 | unpack_to_rootfs+0x2a8/0x3fc | do_populate_rootfs+0xe8/0x11c | async_run_entry_fn+0x58/0x1bc | process_one_work+0x3ec/0x738 | worker_thread+0x4c4/0x838 | kthread+0x20c/0x258 | ret_from_fork+0x10/0x20 | Code: b8bfc2a8 2a0803f7 14000007 d503249f (78bfc2a8) ) | ---[ end trace 613a943cb0a572b6 ]-----

The reason for this is that on certain arm64 configuration since e35123d83ee3 ("arm64: lto: Strengthen READ_ONCE() to acquire when CONFIG_LTO=y"), READ_ONCE() may be promoted to a full atomic acquire instruction which cannot be used on unaligned addresses.

Fix it by avoiding READ_ONCE() in read_instrumented_memory(), and simply forcing the compiler to do the required access by casting to the appropriate volatile type. In terms of generated code this currently only affects architectures that do not use the default READ_ONCE() implementation.

The only downside is that we are not guaranteed atomicity of the access itself, although on most architectures a plain load up to machine word size should still be atomic (a fact the default READ_ONCE() still relies on itself).

CVSS v3
—
EchelonGraph score
Not yet assessedNo source has published severity data for this CVE yet — no CVSS score from NVD or a CNA, no GitHub advisory, and it is not in CISA KEV. This is not a rating of zero; we cannot assess it yet.
EG Score
—
EG Risk
—
EPSS PROB
0%
EPSS %ILE
9%
KEV
Not listed

Published

December 8, 2025

Last Modified

April 15, 2026

References (4)

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 6.1.28—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.

Data Freshness Timeline

(refreshed 8× in last 7d / 43× 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 133 total refreshes for this CVE.

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

Related CVEs(same product)

Frequently asked(4)

What is CVE-2023-53742?
CVE-2023-53742 is a publicly disclosed vulnerability published on December 8, 2025. In the Linux kernel, the following vulnerability has been resolved: kcsan: Avoid READONCE() in readinstrumented_memory() Haibo Li reported: | Unable to handle kernel paging request at virtual address | ffffff802a0d8d7171 | Mem abort info:o: | ESR = 0x9600002121 | EC = 0x25: DABT (current EL), IL =…
When was CVE-2023-53742 disclosed?
CVE-2023-53742 was first published in the National Vulnerability Database on December 8, 2025, with the most recent update on April 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2023-53742 actively exploited?
CVE-2023-53742 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 90.6% of all scored CVEs.
How do I remediate CVE-2023-53742?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2023-53742, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2023-53742

Explore →

Is Your Infrastructure Affected by CVE-2023-53742?

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

Start Free Scan →Browse All CVEs