Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-93191smack: fix incorrect task context in smack_msg_queue_msgrcv

Description

In the Linux kernel, the following vulnerability has been resolved: smack: fix incorrect task context in smack_msg_queue_msgrcv The smack_msg_queue_msgrcv() function incorrectly checks the permissions of the 'current' task instead of the 'target' task. In the msgsnd() syscall path, if a receiver is already waiting, the pipelined_send() optimization is used to push the message directly to the receiver task: ipc/msg.c`pipelined_send(): ` smp_store_release(&msr->r_msg, msg) In this case, the 'sender' (current) task performs the check on behalf of the 'receiver' task (msr->r_tsk, passed as the 'target' parameter): ipc/msg.c`pipelined_send(): ` security_msg_queue_msgrcv(,, target := msr->r_tsk,,) However, smack_msg_queue_msgrcv() ignores the 'target' and checks 'current': smack_msg_queue_msgrcv(…) ` smk_curacc_msq(isp, MAY_READWRITE); // current task 'current' MAY satisfy smack_msg_queue_msgrcv r/w requirement, but 'target' (the receiver task) might NOT; as a result, an unauthorized receiver gets the message, violating MAC policy. Test: 1) create a sysv message queue with label “foo” 2) echo "bar foo r" >/smack/load2 3) msgrcv(,,,0,MSG_NOERROR) in "bar"-labeled task. The task is waiting for the messages ... 4) msgsnd() from a "foo"-labeled task: "bar"-labeled task gets the message. This patch fixes the issue by checking permission on the 'target' task instead of 'current'. (2008-02-04, Casey Schaufler)

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 32 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.20% · top 91% of all CVEs (14 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected e114e473771c848c3cfec05f0123e70f1cdbdc99 – < 4e49f997ef0c569e09b42aab6bd38c7c54ea095d
    • affected e114e473771c848c3cfec05f0123e70f1cdbdc99 – < dbece6c2f80b0470d8d99d7a016827dce99ed6e3
    • affected e114e473771c848c3cfec05f0123e70f1cdbdc99 – < 7be4bd21c50afa83c93799b0f16cf5bfa493194e
    • affected e114e473771c848c3cfec05f0123e70f1cdbdc99 – < ec47f4177046dfaaf1cebb15f4d2e7b543475daf
    • affected e114e473771c848c3cfec05f0123e70f1cdbdc99 – < e35dc5a4ed6d1e536382d80c685187511ff248a1
    • affected e114e473771c848c3cfec05f0123e70f1cdbdc99 – < c2ab27c2e11591524b1378c24ad18882a425d1fa
    • affected e114e473771c848c3cfec05f0123e70f1cdbdc99 – < d02c55e3ea82e41ea2c2026e08201e5daa4d0cfe
    • affected e114e473771c848c3cfec05f0123e70f1cdbdc99 – < fba3d32825f4bbc8e20f0cdc3b14df57965b8fe5
  • Linux · Linux

    • affected 2.6.25
    • unaffected < 2.6.25
    • unaffected 5.10.270 – ≤ 5.10.*
    • unaffected 5.15.221 – ≤ 5.15.*
    • unaffected 6.1.188 – ≤ 6.1.*
    • unaffected 6.6.157 – ≤ 6.6.*
    • unaffected 6.12.110 – ≤ 6.12.*
    • unaffected 6.18.52 – ≤ 6.18.*
    • unaffected 7.2.6 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-93191 badge
[![CVE-2026-93191](https://cveledger.app/badge/CVE-2026-93191.svg)](https://cveledger.app/cve/CVE-2026-93191)

Record last updated .