CVE-2025-68183

HIGHPre-NVD 7.87.8
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2025-12-16. the CNA's CVSS baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

A fix is available — apply it.

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

ima: don't clear IMA_DIGSIG flag when setting or removing non-IMA xattr

Currently when both IMA and EVM are in fix mode, the IMA signature will be reset to IMA hash if a program first stores IMA signature in security.ima and then writes/removes some other security xattr for the file.

For example, on Fedora, after booting the kernel with "ima_appraise=fix evm=fix ima_policy=appraise_tcb" and installing rpm-plugin-ima, installing/reinstalling a package will not make good reference IMA signature generated. Instead IMA hash is generated,

# getfattr -m - -d -e hex /usr/bin/bash # file: usr/bin/bash security.ima=0x0404...

This happens because when setting security.selinux, the IMA_DIGSIG flag that had been set early was cleared. As a result, IMA hash is generated when the file is closed.

Similarly, IMA signature can be cleared on file close after removing security xattr like security.evm or setting/removing ACL.

Prevent replacing the IMA file signature with a file hash, by preventing the IMA_DIGSIG flag from being reset.

Here's a minimal C reproducer which sets security.selinux as the last step which can also replaced by removing security.evm or setting ACL,

#include #include #include #include #include #include

int main() { const char* file_path = "/usr/sbin/test_binary"; const char* hex_string = "030204d33204490066306402304"; int length = strlen(hex_string); char* ima_attr_value; int fd;

fd = open(file_path, O_WRONLY|O_CREAT|O_EXCL, 0644); if (fd == -1) { perror("Error opening file"); return 1; }

ima_attr_value = (char*)malloc(length / 2 ); for (int i = 0, j = 0; i < length; i += 2, j++) { sscanf(hex_string + i, "%2hhx", &ima_attr_value[j]); }

if (fsetxattr(fd, "security.ima", ima_attr_value, length/2, 0) == -1) { perror("Error setting extended attribute"); close(fd); return 1; }

const char* selinux_value= "system_u:object_r:bin_t:s0"; if (fsetxattr(fd, "security.selinux", selinux_value, strlen(selinux_value), 0) == -1) { perror("Error setting extended attribute"); close(fd); return 1; }

close(fd);

return 0; }

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
40(Track)
EG Risk 40/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
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
5%
KEV
Not listed

Published

December 16, 2025

Last Modified

August 5, 2026

Advisory Details (4)

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

ima: don't clear IMA_DIGSIG flag when setting or removing non-IMA xattr - kernel/git/stable/linux.git - Linux kernel stable tree

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

ima: don't clear IMA_DIGSIG flag when setting or removing non-IMA xattr - kernel/git/stable/linux.git - Linux kernel stable tree

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

ima: don't clear IMA_DIGSIG flag when setting or removing non-IMA xattr - kernel/git/stable/linux.git - Linux kernel stable tree

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

ima: don't clear IMA_DIGSIG flag when setting or removing non-IMA xattr - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/02aa671c08a4834bef5166743a7b88686fbfa023

Patch Availability(28)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatkernel-0:4.18.0-305.199.1.el8_42026-07-30redhat
redhatkernel-0:4.18.0-477.152.1.el8_82026-07-16redhat
redhatkernel-0:4.18.0-372.201.1.el8_62026-07-15redhat
redhatkernel-0:6.12.0-55.88.1.el10_02026-07-14redhat
redhatkernel-0:5.14.0-570.127.1.el9_62026-07-13redhat
redhatkernel-0:5.14.0-427.136.1.el9_42026-07-08redhat
redhatkernel-0:5.14.0-284.179.1.el9_22026-07-07redhat
redhatkernel-rt-0:5.14.0-284.179.1.rt14.464.el9_22026-07-06redhat
redhatkernel-0:4.18.0-553.126.1.el8_102026-05-28redhat
redhatkernel-0:6.12.0-211.18.1.el10_22026-05-28redhat
redhatkernel-rt-0:4.18.0-553.126.1.rt7.467.el8_102026-05-28redhat
redhatkernel-0:5.14.0-687.12.1.el9_82026-05-28redhat
ubuntulinux-xilinx-zynqmp (6.8.0.1029.30) @ noble2026-05-21ubuntu
ubuntulinux-tools-azure-6.17 (6.17.0-1008.8) @ questing2026-05-21ubuntu
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2040.41) @ noble2026-05-21ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1052.58+fips1) @ noble2026-05-21ubuntu
ubuntulinux-tools-oracle-64k-6.17 (6.17.0-1007.7) @ questing2026-05-21ubuntu
ubuntulinux-tools-gcp-64k-6.17 (6.17.0-1007.7) @ questing2026-05-21ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.17.0-14.14) @ questing2026-05-21ubuntu
ubuntulinux-tools-oem-6.17 (6.17.0-1011.11) @ noble2026-05-21ubuntu
ubuntulinux-virtual-6.8 (6.8.0-106.106) @ noble2026-05-21ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1049.52.1) @ noble2026-05-21ubuntu
ubuntulinux-tools-gcp-fips-6.8 (6.8.0-1052.55+fips1) @ noble2026-05-21ubuntu
ubuntulinux-tools-realtime-6.8.1 (6.8.1-1045.46) @ noble2026-05-21ubuntu
ubuntulinux-tools-aws-edge (6.8.0-1050.53~22.04.1) @ jammy2026-05-21ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1051.57) @ noble2026-05-21ubuntu
ubuntulinux-tools-azure-edge (6.8.0-1051.57~22.04.1) @ jammy2026-05-21ubuntu
linuxKernel @ 6.6.117osv

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

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 7.2~rc7-1~exp1 (350 versions)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.63-1~bpo12+1 (8 versions)6.12.63-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.17.8-1~bpo13+1 (79 versions)6.17.8-1

Additional Vendor Advisories

(13)

Data Freshness Timeline

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

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

Frequently asked(5)

What is CVE-2025-68183?
CVE-2025-68183 is a high vulnerability published on December 16, 2025. In the Linux kernel, the following vulnerability has been resolved: ima: don't clear IMA_DIGSIG flag when setting or removing non-IMA xattr Currently when both IMA and EVM are in fix mode, the IMA signature will be reset to IMA hash if a program first stores IMA signature in security.ima and then…
When was CVE-2025-68183 disclosed?
CVE-2025-68183 was first published in the National Vulnerability Database on December 16, 2025, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-68183 actively exploited?
CVE-2025-68183 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 95.1% of all scored CVEs.
What is the CVSS score of CVE-2025-68183?
CVE-2025-68183 has a CVSS v4.0 base score of 7.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2025-68183?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-68183, 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-2025-68183

Explore →

Is Your Infrastructure Affected by CVE-2025-68183?

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