CVE-2025-68183: ima: don't clear IMA_DIGSIG flag when setting or removing non-IMA xattr
Noroxi assessment
Priority: Monitor (action score 31/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.15% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 02aa671c08a4834bef5166743a7b88686fbfa023, 7d9ae9d4d45b28c18ca06ae047aabe09d9639643, 88b4cbcf6b041ae0f2fc8a34554a5b6a83a2b7cd.
Low priority for now. Upgrade to Linux Linux 02aa671c08a4834bef5166743a7b88686fbfa023, 7d9ae9d4d45b28c18ca06ae047aabe09d9639643, 88b4cbcf6b041ae0f2fc8a34554a5b6a83a2b7cd or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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; }
- ALSA-2026:21556
- ALSA-2026:21557
- ALSA-2026:21706
- ALSA-2026:21745
- RHSA-2026:21556
- RHSA-2026:21557
- RHSA-2026:21706
- RHSA-2026:21745
- RHSA-2026:35904
- RHSA-2026:36073
- RHSA-2026:36767
- RHSA-2026:38902
- RHSA-2026:39371
- RHSA-2026:40068
- RHSA-2026:40760
- RHSA-2026:47633
- RLSA-2026:21556
- RLSA-2026:21557
- RLSA-2026:21706
- RLSA-2026:21745
- Published
- Dec 16, 2025
- Updated
- Oct 30, 2026
- EPSS
- 0.1% · 4th percentile
- CWE
- —
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 7.8
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 5.14affected
- e3ccfe1ad7d895487977ef64eda3441d16c9851a and later · before 7d9ae9d4d45b28c18ca06ae047aabe09d9639643affected · git
- e3ccfe1ad7d895487977ef64eda3441d16c9851a and later · before d2993a7e98eb70c737c6f5365a190e79c72b8407affected · git
- e3ccfe1ad7d895487977ef64eda3441d16c9851a and later · before edd824eb45e4f7e05ad3ab090dab6dbdb79cd292affected · git
- e3ccfe1ad7d895487977ef64eda3441d16c9851a and later · before 02aa671c08a4834bef5166743a7b88686fbfa023affected · git
- e3ccfe1ad7d895487977ef64eda3441d16c9851a and later · before 88b4cbcf6b041ae0f2fc8a34554a5b6a83a2b7cdaffected · git
- before 5.14not affected · semver
- 6.1.191 and later · up to and including 6.1.*not affected · semver
- 6.6.117 and later · up to and including 6.6.*not affected · semver
- 6.12.58 and later · up to and including 6.12.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:10 | kernel | before 6.12.0-211.18.1.el10_2 | 6.12.0-211.18.1.el10_2 |
| AlmaLinux:10 | kernel-64k | before 6.12.0-211.18.1.el10_2 | 6.12.0-211.18.1.el10_2 |
| AlmaLinux:10 | kernel-64k-core | before 6.12.0-211.18.1.el10_2 | 6.12.0-211.18.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug | before 6.12.0-211.18.1.el10_2 | 6.12.0-211.18.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-core | before 6.12.0-211.18.1.el10_2 | 6.12.0-211.18.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-devel | before 6.12.0-211.18.1.el10_2 | 6.12.0-211.18.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-devel-matched | before 6.12.0-211.18.1.el10_2 | 6.12.0-211.18.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-modules | before 6.12.0-211.18.1.el10_2 | 6.12.0-211.18.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-modules-core | before 6.12.0-211.18.1.el10_2 | 6.12.0-211.18.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-modules-extra | before 6.12.0-211.18.1.el10_2 | 6.12.0-211.18.1.el10_2 |
| AlmaLinux:10 | kernel-64k-devel | before 6.12.0-211.18.1.el10_2 | 6.12.0-211.18.1.el10_2 |
| AlmaLinux:10 | kernel-64k-devel-matched | before 6.12.0-211.18.1.el10_2 | 6.12.0-211.18.1.el10_2 |
| AlmaLinux:10 | kernel-64k-modules | before 6.12.0-211.18.1.el10_2 | 6.12.0-211.18.1.el10_2 |
| AlmaLinux:10 | kernel-64k-modules-core | before 6.12.0-211.18.1.el10_2 | 6.12.0-211.18.1.el10_2 |
| AlmaLinux:10 | kernel-64k-modules-extra | before 6.12.0-211.18.1.el10_2 | 6.12.0-211.18.1.el10_2 |
| AlmaLinux:10 | kernel-abi-stablelists | before 6.12.0-211.18.1.el10_2 | 6.12.0-211.18.1.el10_2 |
| AlmaLinux:10 | kernel-core | before 6.12.0-211.18.1.el10_2 | 6.12.0-211.18.1.el10_2 |
| AlmaLinux:10 | kernel-cross-headers | before 6.12.0-211.18.1.el10_2 | 6.12.0-211.18.1.el10_2 |
| AlmaLinux:10 | kernel-debug | before 6.12.0-211.18.1.el10_2 | 6.12.0-211.18.1.el10_2 |
| AlmaLinux:10 | kernel-debug-core | before 6.12.0-211.18.1.el10_2 | 6.12.0-211.18.1.el10_2 |
| AlmaLinux:10 | kernel-debug-devel | before 6.12.0-211.18.1.el10_2 | 6.12.0-211.18.1.el10_2 |
| AlmaLinux:10 | kernel-debug-devel-matched | before 6.12.0-211.18.1.el10_2 | 6.12.0-211.18.1.el10_2 |
| AlmaLinux:10 | kernel-debug-modules | before 6.12.0-211.18.1.el10_2 | 6.12.0-211.18.1.el10_2 |
| AlmaLinux:10 | kernel-debug-modules-core | before 6.12.0-211.18.1.el10_2 | 6.12.0-211.18.1.el10_2 |
+96
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2025-68181Dec 16, 2025 · drm/radeon: Remove calls to drm_put_dev()31Monitor
- ← EarlierCVE-2025-68182Dec 16, 2025 · wifi: iwlwifi: fix potential use after free in iwl_mld_remove_link()30Monitor
- Later →CVE-2025-68184Dec 16, 2025 · drm/mediatek: Disable AFBC support on Mediatek DRM driver28Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 02aa671c08a4834bef5166743a7b88686fbfa023 | Vendor (CNA) |
| Linux Linux | 7d9ae9d4d45b28c18ca06ae047aabe09d9639643 | Vendor (CNA) |
| Linux Linux | 88b4cbcf6b041ae0f2fc8a34554a5b6a83a2b7cd | Vendor (CNA) |
| Linux Linux | d2993a7e98eb70c737c6f5365a190e79c72b8407 | Vendor (CNA) |
| Linux Linux | edd824eb45e4f7e05ad3ab090dab6dbdb79cd292 | Vendor (CNA) |
| almalinux:kernel | 5.14.0-687.12.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k | 5.14.0-687.12.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-core | 5.14.0-687.12.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug | 5.14.0-687.12.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-core | 5.14.0-687.12.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-devel | 5.14.0-687.12.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-devel-matched | 5.14.0-687.12.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules | 5.14.0-687.12.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules-core | 5.14.0-687.12.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules-extra | 5.14.0-687.12.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-devel | 5.14.0-687.12.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-devel-matched | 5.14.0-687.12.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| debian:linux | 6.12.63-1 · Debian:13 | Package registry (OSV) |
| red hat:kernel-64k-debug-debuginfo | 0:5.14.0-687.12.1.el9_8 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-devel | 0:5.14.0-687.12.1.el9_8 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-devel-matched | 0:5.14.0-687.12.1.el9_8 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-debuginfo | 0:5.14.0-687.12.1.el9_8 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-devel | 0:5.14.0-687.12.1.el9_8 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-devel-matched | 0:5.14.0-687.12.1.el9_8 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-debug-debuginfo | 0:5.14.0-687.12.1.el9_8 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-debug-devel | 0:5.14.0-687.12.1.el9_8 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-debug-devel-matched | 0:5.14.0-687.12.1.el9_8 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-debuginfo | 0:5.14.0-687.12.1.el9_8 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-debuginfo-common-aarch64 | 0:5.14.0-687.12.1.el9_8 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-debuginfo-common-ppc64le | 0:5.14.0-687.12.1.el9_8 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
+2
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.