Threats Tagged 'cve-2026-46104'
View all threats tagged with 'cve-2026-46104'. Filter and sort to focus on specific types of threats.
Stop chasing alerts. Route them.
Start free, then upgrade once to turn Radar into an automated delivery engine for your security stack.
Custom feeds / Automations: email, Slack, webhooks, SIEM/MISP / API access (baseline limits)
API access activates after upgrading in Console -> Billing.
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.
Filter Threats
Narrow down the results by type, severity, or affected countries
Threats Tagged 'cve-2026-46104'
Click on any threat for detailed analysis and mitigation recommendations
A vulnerability in the Linux kernel SELinux socket permission helpers was identified where direct access to sk->sk_security assumed the SELinux socket blob was at offset zero. This assumption fails in stacked LSM configurations, potentially causing incorrect security identifiers and classes to be used in permission checks. The issue was resolved by using the selinux_sock() accessor instead of direct sk_security access. Join the discussion | GCVE Database | 05/28/2026, 12:30:28 UTC Added: 06/26/2026, 22:06:37 UTC |
In the Linux kernel, the following vulnerability has been resolved: selinux: use sk blob accessor in socket permission helpers SELinux socket state lives in the composite LSM socket blob. sock_has_perm() and nlmsg_sock_has_extended_perms() currently dereference sk->sk_security directly, which assumes the SELinux socket blob is at offset zero. In stacked configurations that assumption does not hold. If another LSM allocates socket blob storage before SELinux, these helpers may read the wrong blob and feed invalid SID and class values into AVC checks. Use selinux_sock() instead of accessing sk->sk_security directly. Join the discussion | GCVE Database | 05/28/2026, 10:16:00 UTC Added: 07/17/2026, 10:20:57 UTC |
Showing 1 to 2 of 2 results