AI News Intel

In the Linux kernel, the following vulnerability has been resolved: KEYS: Fix...

0.62
nvd-cves · v2 · published 11/3/2026, 12:31:49 PM · modified 11/3/2026, 12:31:54 PM · TLP:CLEAR
offsec.vulnerability
Source evidence ↗

Entities

ghsa: GHSA-g5g7-wfj6-x845cve: CVE-2026-99245

Assessment

Fact summary

low · heuristic

In the Linux kernel, the following vulnerability has been resolved: KEYS: Fix key_reject_and_link() race with keyring restriction The restrict_link check in key_reject_and_link() is done before taking the keyring semaphore, racing with a concurrent keyring_restrict() that installs the restriction while holding the semaphore in write mode. Move the check to after __key_link_lock(), so it is done under the semaphore, matching the pattern used in __key_create_or_update(). Weaknesses:

Technical delta

low · heuristic

Automated delta unavailable (heuristic mode).

Defensive significance

low · heuristic

None identified (heuristic mode).

Fact summary

low · heuristic

In the Linux kernel, the following vulnerability has been resolved: KEYS: Fix key_reject_and_link() race with keyring restriction The restrict_link check in key_reject_and_link() is done before taking the keyring semaphore, racing with a concurrent keyring_restrict() that installs the restriction while holding the semaphore in write mode. Move the check to after __key_link_lock(), so it is done under the semaphore, matching the pattern used in __key_create_or_update().

Technical delta

low · heuristic

Automated delta unavailable (heuristic mode).

Defensive significance

low · heuristic

None identified (heuristic mode).

Extracted text

In the Linux kernel, the following vulnerability has been resolved:

KEYS: Fix key_reject_and_link() race with keyring restriction

The restrict_link check in key_reject_and_link() is done before taking
the keyring semaphore, racing with a concurrent keyring_restrict()
that installs the restriction while holding the semaphore in write
mode.

Move the check to after __key_link_lock(), so it is done under the
semaphore, matching the pattern used in __key_create_or_update().