CVE-2024-36031·Kernel vulnerability
In the Linux kernel, the following vulnerability has been resolved: keys: Fix overwrite of key expiration on instantiation The expiry time of a key is unconditionally overwritten during instantiation, defaulting to turn it permanent. This causes a problem for DNS resolution as the expiration set by user-space is overwritten to TIME64_MAX, disabling further DNS updates. Fix this by restoring the condition that key_set_expiry is only called when the pre-parser sets a specific expiry.
- Severity
- critical
- Software
- Kernel
- Fixed in
- 6.9.1
- Published
- 2024-05-30
Affected versions
From: 6.9
Until: 6.9.1
Fixed in: 6.9.1
How to fix this CVE
Update your Linux kernel to version 6.9.1 or later to fix the key expiration handling issue that was causing DNS resolution failures. This patch restores proper conditional logic for setting key expiry times, preventing user-space configured expirations from being overwritten to permanent. Kernel updates typically require a system reboot to take effect.
sudo dnf update kernel kernel-devel && sudo rebootDefensia detects this vulnerability
How to check if you are affected
- Check kernel version: uname -r — verify if it is between 6.9 and 6.9.1 (vulnerable range)
- Confirm the kernel-keys subsystem is in use: cat /proc/keys | head -5 — look for key entries to verify key management is active
- Monitor DNS resolution failures: grep -i 'dns.*timeout\|dns.*fail' /var/log/syslog or journalctl -u systemd-resolved | grep -i error to detect DNS query failures caused by expired key caching
- Verify the patch: cat /boot/config-$(uname -r) | grep CONFIG_KEYS to ensure the fixed kernel version contains key management support, then compare kernel version against 6.9.1+
FAQ
What is CVE-2024-36031?
This vulnerability exists in the Linux kernel's key management subsystem, where key expiration times are unconditionally reset to permanent (TIME64_MAX) during instantiation. This breaks DNS caching mechanisms that rely on time-limited key validity, causing DNS resolution to fail or stall.
Is CVE-2024-36031 being actively exploited?
No, this CVE is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog and no public exploit code is currently available. However, it causes significant operational impact to DNS services and should be patched promptly.
What versions of Kernel are affected by CVE-2024-36031?
Linux kernel versions 6.9 through 6.9.1 are vulnerable. The fix is included in kernel 6.9.1 and all subsequent releases.
How do I check if my server is vulnerable to CVE-2024-36031?
Run uname -r and check if the output is 6.9 or 6.9.1. If it shows 6.9.0, 6.9, or 6.9.1, your system is vulnerable and requires an immediate kernel update to 6.9.2 or later.
Does Defensia detect CVE-2024-36031?
Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If Kernel is installed on a monitored server, CVE-2024-36031 will appear in your dashboard with remediation steps.
Related Kernel CVEs
References
- https://git.kernel.org/stable/c/25777f3f4e1f371d16a594925f31e37ce07b6ec7
- https://git.kernel.org/stable/c/939a08bcd4334bad4b201e60bd0ae1f278d71d41
- https://git.kernel.org/stable/c/9da27fb65a14c18efd4473e2e82b76b53ba60252
- https://git.kernel.org/stable/c/ad2011ea787928b2accb5134f1e423b11fe80a8a
- https://git.kernel.org/stable/c/cc219cb8afbc40ec100c0de941047bb29373126a
Track CVEs across your fleet automatically
Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2024-36031. Free for 1 server.
Get started free