DNS refresh disruption via immortalized resolver keys
Published May 30, 2024 · Updated May 23, 2026
Improper key expiration handling in affected Linux kernel releases allows local users to prevent DNS resolver key refreshes. In security/keys/key.c, key instantiation calls key_set_expiry unconditionally, replacing a user-space expiration with TIME64_MAX when the pre-parser supplied no specific expiry. Reachability requires local high-privileged access to instantiate the relevant key; affected DNS resolver keys become permanent, so later DNS updates remain disabled.
Summary
What happened
Improper key expiration handling in affected Linux kernel releases allows local users to prevent DNS resolver key refreshes. In security/keys/key.c, key instantiation calls key_set_expiry unconditionally, replacing a user-space expiration with TIME64_MAX when the pre-parser supplied no specific expiry. Reachability requires local high-privileged access to instantiate the relevant key; affected DNS resolver keys become permanent, so later DNS updates remain disabled.
The record
- CVE
- CVE-2024-36031
- Published
- May 30, 2024
- Updated
- May 23, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-324
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- May 30, 2024CVE publishedPublication date reported by the CVE source.
- May 23, 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=2552b32b0b349df160a509fe49f5f308cb922f2b <ed79b93f725cd0da39a265dc23d77add1527b9be
- Affected versionversion=39299bdd2546688d92ed9db4948f6219ca1b9542 <939a08bcd4334bad4b201e60bd0ae1f278d71d41
- Affected versionversion=39299bdd2546688d92ed9db4948f6219ca1b9542 <9da27fb65a14c18efd4473e2e82b76b53ba60252
- Affected versionversion=39299bdd2546688d92ed9db4948f6219ca1b9542 <cc219cb8afbc40ec100c0de941047bb29373126a
- Affected versionversion=5.10.206 <5.10.217
- Affected versionversion=5.15.146 <5.15.159
- Affected versionversion=6.1.70 <6.1.91
- Affected versionversion=6.6.9 <6.6.31
- Affected versionversion=6.7
- Affected versionversion=791d5409cdb974c31a1bc7a903ea729ddc7d83df <e4519a016650e952ad9eb27937f8c447d5a4e06d
- Affected versionversion=97be1e865e70e5a0ad0a5b5f5dca5031ca0b53ac <ad2011ea787928b2accb5134f1e423b11fe80a8a
- Affected versionversion=afc360e8a1256acb7579a6f5b6f2c30b85b39301 <25777f3f4e1f371d16a594925f31e37ce07b6ec7
What conditions does exploitation require?
What is affected?
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