https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 03 Oct 2026 22:02:16 +0000 https://cve.radiocsirt.org/vuln/bell-cve-2026-52906 <p><strong>Withdrawn by the publisher.</strong></p> <p><strong>Withdrawn by the publisher.</strong></p> https://cve.radiocsirt.org/vuln/bell-cve-2026-52906 https://cve.radiocsirt.org/vuln/certfr-2026-avi-0831 certfr-2026-avi-0831 https://cve.radiocsirt.org/vuln/certfr-2026-avi-0831 https://cve.radiocsirt.org/vuln/euvd-2026-348084 EUVD-2026-348084 https://cve.radiocsirt.org/vuln/euvd-2026-348084 https://cve.radiocsirt.org/vuln/fkie_cve-2026-52906 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>9p: fix access mode flags being ORed instead of replaced</p> <p>Since commit 1f3e4142c0eb (&#34;9p: convert to the new mount API&#34;), v9fs_apply_options() applies parsed mount flags with |= onto flags already set by v9fs_session_init(). For 9P2000.L, session_init sets V9FS_ACCESS_CLIENT as the default, so when the user mounts with &#34;access=user&#34;, both bits end up set. Access mode checks compare against exact values, so having both bits set matches neither mode.</p> <p>This causes v9fs_fid_lookup() to fall through to the default switch case, using INVALID_UID (nobody/65534) instead of current_fsuid() for all fid lookups. Root is then unable to chown or perform other privileged operations.</p> <p>Fix by clearing the access mask before applying the user&#39;s choice.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>9p: fix access mode flags being ORed instead of replaced</p> <p>Since commit 1f3e4142c0eb (&#34;9p: convert to the new mount API&#34;), v9fs_apply_options() applies parsed mount flags with |= onto flags already set by v9fs_session_init(). For 9P2000.L, session_init sets V9FS_ACCESS_CLIENT as the default, so when the user mounts with &#34;access=user&#34;, both bits end up set. Access mode checks compare against exact values, so having both bits set matches neither mode.</p> <p>This causes v9fs_fid_lookup() to fall through to the default switch case, using INVALID_UID (nobody/65534) instead of current_fsuid() for all fid lookups. Root is then unable to chown or perform other privileged operations.</p> <p>Fix by clearing the access mask before applying the user&#39;s choice.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2026-52906 https://cve.radiocsirt.org/vuln/ghsa-4vm9-m655-vqf4 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>9p: fix access mode flags being ORed instead of replaced</p> <p>Since commit 1f3e4142c0eb (&#34;9p: convert to the new mount API&#34;), v9fs_apply_options() applies parsed mount flags with |= onto flags already set by v9fs_session_init(). For 9P2000.L, session_init sets V9FS_ACCESS_CLIENT as the default, so when the user mounts with &#34;access=user&#34;, both bits end up set. Access mode checks compare against exact values, so having both bits set matches neither mode.</p> <p>This causes v9fs_fid_lookup() to fall through to the default switch case, using INVALID_UID (nobody/65534) instead of current_fsuid() for all fid lookups. Root is then unable to chown or perform other privileged operations.</p> <p>Fix by clearing the access mask before applying the user&#39;s choice.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>9p: fix access mode flags being ORed instead of replaced</p> <p>Since commit 1f3e4142c0eb (&#34;9p: convert to the new mount API&#34;), v9fs_apply_options() applies parsed mount flags with |= onto flags already set by v9fs_session_init(). For 9P2000.L, session_init sets V9FS_ACCESS_CLIENT as the default, so when the user mounts with &#34;access=user&#34;, both bits end up set. Access mode checks compare against exact values, so having both bits set matches neither mode.</p> <p>This causes v9fs_fid_lookup() to fall through to the default switch case, using INVALID_UID (nobody/65534) instead of current_fsuid() for all fid lookups. Root is then unable to chown or perform other privileged operations.</p> <p>Fix by clearing the access mask before applying the user&#39;s choice.</p> https://cve.radiocsirt.org/vuln/ghsa-4vm9-m655-vqf4 https://cve.radiocsirt.org/vuln/opensuse-su-2026:11014-1 <p>kernel-devel-7.0.12-1.1 on GA media</p> <p>kernel-devel-7.0.12-1.1 on GA media</p> https://cve.radiocsirt.org/vuln/opensuse-su-2026:11014-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-52906 <p><strong>Affected:</strong> Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 98 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: 9p: fix access mode flags being ORed instead of replaced Since commit 1f3e4142c0eb (&#34;9p: convert to the new mount API&#34;), v9fs_apply_options() applies parsed mount flags with |= onto flags already set by v9fs_session_init(). For 9P2000.L, session_init sets V9FS_ACCESS_CLIENT as the default, so when the user mounts with &#34;access=user&#34;, both bits end up set. Access mode checks compare against exact values, so having both bits set matches neither mode. This causes v9fs_fid_lookup() to fall through to the default switch case, using INVALID_UID (nobody/65534) instead of current_fsuid() for all fid lookups. Root is then unable to chown or perform other privileged operations. Fix by clearing the access mask before applying the user&#39;s choice.</p> <p><strong>Affected:</strong> Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 98 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: 9p: fix access mode flags being ORed instead of replaced Since commit 1f3e4142c0eb (&#34;9p: convert to the new mount API&#34;), v9fs_apply_options() applies parsed mount flags with |= onto flags already set by v9fs_session_init(). For 9P2000.L, session_init sets V9FS_ACCESS_CLIENT as the default, so when the user mounts with &#34;access=user&#34;, both bits end up set. Access mode checks compare against exact values, so having both bits set matches neither mode. This causes v9fs_fid_lookup() to fall through to the default switch case, using INVALID_UID (nobody/65534) instead of current_fsuid() for all fid lookups. Root is then unable to chown or perform other privileged operations. Fix by clearing the access mask before applying the user&#39;s choice.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-52906 https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1870 <p>Eiin Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial-of-Service-Zustand zu erzeugen oder andere, nicht näher bezeichnete Angriffe durchzuführen.</p> <p>Eiin Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial-of-Service-Zustand zu erzeugen oder andere, nicht näher bezeichnete Angriffe durchzuführen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1870