CVE-2025-68183ima: don't clear IMA_DIGSIG flag when setting or removing non-IMA xattr
- 7.8HighCVSS base score
- 0.15%Exploitation in 30 daysEPSS · top 95% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
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 <stdio.h> #include <sys/xattr.h> #include <fcntl.h> #include <unistd.h> #include <string.h> #include <stdlib.h> 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; }
Timeline
ID reserved
By Linux
Published
- 11 months later
· 11 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVDNVD · Deferred | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
- EPSS (exploitation in 30 days)
- 0.15% · top 95% of all CVEs (13 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: total
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.
Affected products
- affected e3ccfe1ad7d895487977ef64eda3441d16c9851a – < 7d9ae9d4d45b28c18ca06ae047aabe09d9639643
- affected e3ccfe1ad7d895487977ef64eda3441d16c9851a – < d2993a7e98eb70c737c6f5365a190e79c72b8407
- affected e3ccfe1ad7d895487977ef64eda3441d16c9851a – < edd824eb45e4f7e05ad3ab090dab6dbdb79cd292
- affected e3ccfe1ad7d895487977ef64eda3441d16c9851a – < 02aa671c08a4834bef5166743a7b88686fbfa023
- affected e3ccfe1ad7d895487977ef64eda3441d16c9851a – < 88b4cbcf6b041ae0f2fc8a34554a5b6a83a2b7cd
- affected 5.14
- unaffected < 5.14
- unaffected 6.1.191 – ≤ 6.1.*
- unaffected 6.6.117 – ≤ 6.6.*
- unaffected 6.12.58 – ≤ 6.12.*
- unaffected 6.17.8 – ≤ 6.17.*
- unaffected 6.18 – ≤ *
References
References5
- https://git.kernel.org/stable/c/7d9ae9d4d45b28c18ca06ae047aabe09d9639643 (opens in a new tab)
- https://git.kernel.org/stable/c/d2993a7e98eb70c737c6f5365a190e79c72b8407 (opens in a new tab)
- https://git.kernel.org/stable/c/edd824eb45e4f7e05ad3ab090dab6dbdb79cd292 (opens in a new tab)
- https://git.kernel.org/stable/c/02aa671c08a4834bef5166743a7b88686fbfa023 (opens in a new tab)
- https://git.kernel.org/stable/c/88b4cbcf6b041ae0f2fc8a34554a5b6a83a2b7cd (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2025-203713 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2025-68183)Record last updated .