{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-93191 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-93191 is a vulnerability in Linux, published on 17 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-93191 and fix it if it is affected.\n\nWhat it is: CVE-2026-93191 is a vulnerability in Linux, published on 17 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-93191 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-93191/ (Markdown: https://insights.sbomify.com/CVE-2026-93191/index.md)","id":"CVE-2026-93191","markdown":"https://insights.sbomify.com/CVE-2026-93191/index.md","name":"CVE-2026-93191","record":{"aliases":["AZL-102807","BELL-CVE-2026-93191","DEBIAN-CVE-2026-93191","GHSA-9697-g343-86c8","UBUNTU-CVE-2026-93191"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["data_read","security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Linux kernel","requires_auth":"low_privilege","summary":"A flaw in the Linux kernel SMACK module allows unauthorized local users to read messages from System V message queues, bypassing Mandatory Access Control policies.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nsmack: fix incorrect task context in smack_msg_queue_msgrcv\n\nThe smack_msg_queue_msgrcv() function incorrectly checks\nthe permissions of the 'current' task instead of the\n'target' task.\n\nIn the msgsnd() syscall path, if a receiver is already waiting,\nthe pipelined_send() optimization is used to push the message\ndirectly to the receiver task:\n\n    ipc/msg.c`pipelined_send():\n    ` smp_store_release(\u0026msr-\u003er_msg, msg)\n\nIn this case, the 'sender' (current) task performs the check\non behalf of the 'receiver' task (msr-\u003er_tsk, passed as the\n'target' parameter):\n\n  ipc/msg.c`pipelined_send():\n  ` security_msg_queue_msgrcv(,, target := msr-\u003er_tsk,,)\n\nHowever, smack_msg_queue_msgrcv() ignores the 'target' and\nchecks 'current':\n\n  smack_msg_queue_msgrcv(…)\n  ` smk_curacc_msq(isp, MAY_READWRITE); // current task\n\n'current' MAY satisfy smack_msg_queue_msgrcv r/w requirement,\nbut 'target' (the receiver task) might NOT;\nas a result, an unauthorized receiver gets the message,\nviolating MAC policy.\n\nTest:\n1) create a sysv message queue with label “foo”\n2) echo \"bar foo r\" \u003e/smack/load2\n3) msgrcv(,,,0,MSG_NOERROR) in \"bar\"-labeled task.\n    The task is waiting for the messages ...\n4) msgsnd() from a \"foo\"-labeled task:\n\"bar\"-labeled task gets the message.\n\nThis patch fixes the issue by checking permission on the\n'target' task instead of 'current'.\n\n(2008-02-04, Casey Schaufler)","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"smack: fix incorrect task context in smack_msg_queue_msgrcv","id":"CVE-2026-93191","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":0,"n_references":8,"next":{"headline":"drm/v3d: Clear queue-\u003eactive_job when v3d_fence_create() fails","id":"CVE-2026-93192"},"packages":[],"prev":{"headline":"platform/chrome: cros_ec_typec: Reject out-of-bounds PD cap count","id":"CVE-2026-93190"},"products":["Linux"],"published":"2026-09-17","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-19","vendors":["Linux"]},"summary":"A flaw in the Linux kernel SMACK module allows unauthorized local users to read messages from System V message queues, bypassing Mandatory Access Control policies.","url":"https://insights.sbomify.com/CVE-2026-93191/"}