CVE-2026-93191
Last modified
CVE-2026-93191 is a vulnerability of currently unknown severity. 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).
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)
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= e114e473771c848c3cfec05f0123e70f1cdbdc99, < 4e49f997ef0c569e09b42aab6bd38c7c54ea095d; >= e114e473771c848c3cfec05f0123e70f1cdbdc99, < dbece6c2f80b0470d8d99d7a016827dce99ed6e3; >= e114e473771c848c3cfec05f0123e70f1cdbdc99, < 7be4bd21c50afa83c93799b0f16cf5bfa493194e; >= e114e473771c848c3cfec05f0123e70f1cdbdc99, < ec47f4177046dfaaf1cebb15f4d2e7b543475daf; >= e114e473771c848c3cfec05f0123e70f1cdbdc99, < e35dc5a4ed6d1e536382d80c685187511ff248a1; >= e114e473771c848c3cfec05f0123e70f1cdbdc99, < c2ab27c2e11591524b1378c24ad18882a425d1fa; >= e114e473771c848c3cfec05f0123e70f1cdbdc99, < d02c55e3ea82e41ea2c2026e08201e5daa4d0cfe; >= e114e473771c848c3cfec05f0123e70f1cdbdc99, < fba3d32825f4bbc8e20f0cdc3b14df57965b8fe5 |
| Linux | Linux | 2.6.25 |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-93191?
How severe is CVE-2026-93191?
How do I fix CVE-2026-93191?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-93186In the Linux kernel, the following vulnerability has been re…
- CVE-2026-93187In the Linux kernel, the following vulnerability has been re…
- CVE-2026-93188In the Linux kernel, the following vulnerability has been re…
- CVE-2026-93189In the Linux kernel, the following vulnerability has been re…8.8
- CVE-2026-9319IBM WebSphere Application Server 9.0, and 8.5 is vulnerable …9
- CVE-2026-93190In the Linux kernel, the following vulnerability has been re…8.4
- CVE-2026-93192In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-93193In the Linux kernel, the following vulnerability has been re…
- CVE-2026-93194In the Linux kernel, the following vulnerability has been re…
- CVE-2026-93195In the Linux kernel, the following vulnerability has been re…
- CVE-2026-93196In the Linux kernel, the following vulnerability has been re…8.4
- CVE-2026-93197In the Linux kernel, the following vulnerability has been re…
Are you affected by CVE-2026-93191?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
