LiveActive security incident?Get immediate response
CVE Record

CVE-2025-68740: ima: Handle error code returned by ima_filter_rule_match()

In the Linux kernel, the following vulnerability has been resolved: ima: Handle error code returned by ima_filter_rule_match() In ima_match_rules(), if ima_filter_rule_match() returns -ENOENT due to the rule being NULL, the function incorrectly skips the 'if (!rc)' check and sets 'result = true'. The LSM rule is considered a match, causing extra files to be measured by IMA. This issue can be reproduced in the following scenario: After unloading the SELinux policy module via 'semodule -d', if an IMA measurement is triggered before ima_lsm_rules is updated, in ima_match_rules(), the first call to ima_filter_rule_match() returns -ESTALE. This causes the code to enter the 'if (rc == -ESTALE && !rule_reinitialized)' block, perform ima_lsm_copy_rule() and retry. In ima_lsm_copy_rule(), since the SELinux module has been removed, the rule becomes NULL, and the second call to ima_filter_rule_match() returns -ENOENT. This bypasses the 'if (!rc)' check and results in a false match. Call trace: selinux_audit_rule_match+0x310/0x3b8 security_audit_rule_match+0x60/0xa0 ima_match_rules+0x2e4/0x4a0 ima_match_policy+0x9c/0x1e8 ima_get_action+0x48/0x60 process_measurement+0xf8/0xa98 ima_bprm_check+0x98/0xd8 security_bprm_check+0x5c/0x78 search_binary_handler+0x6c/0x318 exec_binprm+0x58/0x1b8 bprm_execve+0xb8/0x130 do_execveat_common.isra.0+0x1a8/0x258 __arm64_sys_execve+0x48/0x68 invoke_syscall+0x50/0x128 el0_svc_common.constprop.0+0xc8/0xf0 do_el0_svc+0x24/0x38 el0_svc+0x44/0x200 el0t_64_sync_handler+0x100/0x130 el0t_64_sync+0x3c8/0x3d0 Fix this by changing 'if (!rc)' to 'if (rc <= 0)' to ensure that error codes like -ENOENT do not bypass the check and accidentally result in a successful match.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue can make Integrity Measurement Architecture treat a failed LSM policy-rule lookup as a match. In the documented scenario, that causes extra files to be measured after a SELinux policy module is unloaded. The source does not show code execution, privilege escalation, data theft, or active exploitation.

Executive priority

Treat as a focused kernel integrity-measurement correctness issue. Prioritize patching where IMA supports compliance, attestation, or high-assurance monitoring; broader emergency response is not supported by the provided evidence.

Technical view

In ima_match_rules(), negative errors from ima_filter_rule_match(), specifically -ENOENT after an -ESTALE retry and NULL rule, could bypass the intended non-match handling and set result=true. The fix changes the condition from !rc to rc <= 0 so error codes cannot become successful IMA rule matches.

Likely exposure

Exposure is most plausible on Linux systems using IMA with LSM/SELinux policy rules, especially where SELinux policy modules may be unloaded while IMA measurements occur. The bundle lists Linux kernels as affected but does not provide distribution package names.

Exploitation context

The source describes a reproducible race-like operational scenario involving SELinux module unloading and IMA rule refresh timing. KEV is false, and the bundle provides no evidence of public exploitation or weaponized abuse.

Researcher notes

The impact shown is false-positive IMA rule matching that measures extra files, not a bypass of measurement. Key edge case: -ESTALE triggers rule copy, removed SELinux module yields NULL rule and -ENOENT, then result was incorrectly set true.

Mitigation direction

  • Apply Linux kernel updates containing the referenced stable fixes.
  • Check distribution vendor advisories for exact fixed kernel package versions.
  • Prioritize systems using IMA and SELinux policy-based measurement rules.
  • Avoid unloading SELinux policy modules on IMA-dependent systems until patched, where operationally feasible.

Validation and detection

  • Inventory Linux hosts using IMA and SELinux policy rules.
  • Compare running kernel versions against vendor fixed packages or referenced stable commits.
  • Review change records for SELinux policy module unload operations.
  • Monitor IMA measurement volume for unexpected increases around SELinux policy changes.
Prepared
Confidence
medium
Sources
6

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2025-68740 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
1ADP providers
9Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux4af4662fa4a9dc62289c580337ae2506339c4729, 4af4662fa4a9dc62289c580337ae2506339c4729, 4af4662fa4a9dc62289c580337ae2506339c4729, 4af4662fa4a9dc62289c580337ae2506339c4729, 4af4662fa4a9dc62289c580337ae2506339c4729, 4af4662fa4a9dc62289c580337ae2506339c4729, 4af4662fa4a9dc62289c580337ae2506339c4729, 4af4662fa4a9dc62289c580337ae2506339c4729unaffected
LinuxLinux2.6.30, 0, 5.10.248, 5.15.198, 6.1.160, 6.6.120, 6.12.63, 6.17.13, 6.18.2, 6.19affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.