CPU-limit bypass via stale POSIX timer state
Published Jun 9, 2026 · Updated Jun 9, 2026
Resource-limit enforcement failure in affected Linux Kernel releases from 4.10 allows local users to bypass AppArmor CPU limits on exec. In security/apparmor/resource.c, the profile-transition path changes RLIMIT_CPU without refreshing the POSIX CPU timer's cached next-expiration state. A confined local process must be allowed to execute into a profile with a different CPU limit; stale state then permits excess CPU use or sends premature SIGXCPU, terminating the process.
Summary
What happened
Resource-limit enforcement failure in affected Linux Kernel releases from 4.10 allows local users to bypass AppArmor CPU limits on exec. In security/apparmor/resource.c, the profile-transition path changes RLIMIT_CPU without refreshing the POSIX CPU timer's cached next-expiration state. A confined local process must be allowed to execute into a profile with a different CPU limit; stale state then permits excess CPU use or sends premature SIGXCPU, terminating the process.
The record
- CVE
- CVE-2026-46328
- Published
- Jun 9, 2026
- Updated
- Jun 9, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- T1496.001
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 9, 2026CVE publishedPublication date reported by the CVE source.
- Jun 9, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=4.10
- Affected versionversion=baa73d9e478ff32d62f3f9422822b59dd9a95a21 <1f736dfe27c857b78f8461cd7c3dd9640be74b37
- Affected versionversion=baa73d9e478ff32d62f3f9422822b59dd9a95a21 <2232d7cd243833ad750cae656d1817fe43744a09
- Affected versionversion=baa73d9e478ff32d62f3f9422822b59dd9a95a21 <28aa93fcfb33b6d580c5df4ae8b6d13fb0e6fcd3
- Affected versionversion=baa73d9e478ff32d62f3f9422822b59dd9a95a21 <57d51d41b90eface809b72e0e009b50546492f1f
- Affected versionversion=baa73d9e478ff32d62f3f9422822b59dd9a95a21 <6ca56813f4a589f536adceb42882855d91fb1125
- Affected versionversion=baa73d9e478ff32d62f3f9422822b59dd9a95a21 <9bf1fa150775b0c6b794e4b6a2c0395e13777999
- Affected versionversion=baa73d9e478ff32d62f3f9422822b59dd9a95a21 <e1cc11550b2f66687a374536c9dfdddcefca0efe
- Affected versionversion=baa73d9e478ff32d62f3f9422822b59dd9a95a21 <e43818b16815c0c2bf933ef28316f8e704e5e0ef
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo