CVE-2026-53038

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2026-06-24. 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%CVSS: 5.5Exploit: None knownExposed: 0

A fix is available — apply it.

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

ima_fs: Correctly create securityfs files for unsupported hash algos

ima_tpm_chip->allocated_banks[i].crypto_id is initialized to HASH_ALGO__LAST if the TPM algorithm is not supported. However there are places relying on the algorithm to be valid because it is accessed by hash_algo_name[].

On 6.12.40 I observe the following read out-of-bounds in hash_algo_name: ================================================================== BUG: KASAN: global-out-of-bounds in create_securityfs_measurement_lists+0x396/0x440 Read of size 8 at addr ffffffff83e18138 by task swapper/0/1

CPU: 4 UID: 0 PID: 1 Comm: swapper/0 Not tainted 6.12.40 #3 Call Trace: dump_stack_lvl+0x61/0x90 print_report+0xc4/0x580 ? kasan_addr_to_slab+0x26/0x80 ? create_securityfs_measurement_lists+0x396/0x440 kasan_report+0xc2/0x100 ? create_securityfs_measurement_lists+0x396/0x440 create_securityfs_measurement_lists+0x396/0x440 ima_fs_init+0xa3/0x300 ima_init+0x7d/0xd0 init_ima+0x28/0x100 do_one_initcall+0xa6/0x3e0 kernel_init_freeable+0x455/0x740 kernel_init+0x24/0x1d0 ret_from_fork+0x38/0x80 ret_from_fork_asm+0x11/0x20

The buggy address belongs to the variable: hash_algo_name+0xb8/0x420

Memory state around the buggy address: ffffffff83e18000: 00 01 f9 f9 f9 f9 f9 f9 00 01 f9 f9 f9 f9 f9 f9 ffffffff83e18080: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 >ffffffff83e18100: 00 00 00 00 00 00 00 f9 f9 f9 f9 f9 00 05 f9 f9 ^ ffffffff83e18180: f9 f9 f9 f9 00 00 00 00 00 00 00 04 f9 f9 f9 f9 ffffffff83e18200: 00 00 00 00 00 00 00 00 04 f9 f9 f9 f9 f9 f9 f9 ==================================================================

Seems like the TPM chip supports sha3_256, which isn't yet in tpm_algorithms: tpm tpm0: TPM with unsupported bank algorithm 0x0027

That's TPM_ALG_SHA3_256 == 0x0027 from "Trusted Platform Module 2.0 Library Part 2: Structures", page 51 [1]. See also the related U-Boot algorithms update [2].

Thus solve the problem by creating a file name with "_tpm_alg_" postfix if the crypto algorithm isn't initialized.

This is how it looks on the test machine (patch ported to v6.12 release): # ls -1 /sys/kernel/security/ima/ ascii_runtime_measurements ascii_runtime_measurements_tpm_alg_27 ascii_runtime_measurements_sha1 ascii_runtime_measurements_sha256 binary_runtime_measurements binary_runtime_measurements_tpm_alg_27 binary_runtime_measurements_sha1 binary_runtime_measurements_sha256 policy runtime_measurements_count violations

[1]: https://trustedcomputinggroup.org/wp-content/uploads/Trusted-Platform-Module-2.0-Library-Part-2-Version-184_pub.pdf [2]: https://lists.denx.de/pipermail/u-boot/2024-July/558835.html

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
29(Track)
EG Risk 29/100SSVC: Track

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%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
2%
KEV
Not listed

Published

June 24, 2026

Last Modified

July 14, 2026

Advisory Details (4)

Auto-updated Jul 16, 2026
No patch confirmed yet.
generic

ima_fs: Correctly create securityfs files for unsupported hash algos - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/d7bd8cf0b348d3edae7bee33e74a32b21668b181
generic

ima_fs: Correctly create securityfs files for unsupported hash algos - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/b6766b171a5c4c33b26ff6fec530cb798db1f75e
generic

ima_fs: Correctly create securityfs files for unsupported hash algos - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/88d4e89a39f0de07798ca3fd93bd1a9ea212a82e
generic

ima_fs: Correctly create securityfs files for unsupported hash algos - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/081b557cb56e1cfa8d1619b2601b01c53e3f418c

Vendor Advisories for CVE-2026-53038(1)

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

Patch Availability(8)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-virtual-hwe-24.04-edge (7.0.0-28.28~24.04.1) @ noble2026-08-30ubuntu
ubuntulinux-tools-oracle-7.0 (7.0.0-1008.8) @ resolute2026-08-30ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1015.15) @ resolute2026-08-30ubuntu
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-28.28) @ resolute2026-08-30ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1009.9) @ resolute2026-08-30ubuntu
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-08-30ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1016.16) @ resolute2026-08-30ubuntu
ubuntulinux-tools-nvidia-hwe-26.04 (7.0.0-2016.16) @ resolute2026-08-30ubuntu

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

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.94-1~bpo12+1 (27 versions)6.12.94-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (140 versions)7.0.10-1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(8)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 4× in last 7d / 58× 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 166 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-53038?
CVE-2026-53038 is a medium vulnerability published on June 24, 2026. In the Linux kernel, the following vulnerability has been resolved: ima_fs: Correctly create securityfs files for unsupported hash algos imatpmchip->allocatedbanks[i].cryptoid is initialized to HASHALGO_LAST if the TPM algorithm is not supported. However there are places relying on the algorithm to…
When was CVE-2026-53038 disclosed?
CVE-2026-53038 was first published in the National Vulnerability Database on June 24, 2026, with the most recent update on July 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53038 actively exploited?
CVE-2026-53038 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 97.8% of all scored CVEs.
What is the CVSS score of CVE-2026-53038?
CVE-2026-53038 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-53038?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53038, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-53038

Explore →

Is Your Infrastructure Affected by CVE-2026-53038?

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

Start Free Scan →Browse All CVEs