https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Thu, 01 Oct 2026 07:35:11 +0000 https://vulnerability.circl.lu/vuln/bell-cve-2026-90226 <p><strong>Affected:</strong> Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts</p> <p><strong>Affected:</strong> Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts</p> https://vulnerability.circl.lu/vuln/bell-cve-2026-90226 https://vulnerability.circl.lu/vuln/fkie_cve-2026-90226 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>nfc: llcp: avoid userspace overflow on invalid optlen</p> <p>nfc_llcp_getsockopt() casts optval to (u32 __user *) for put_user(), so the kernel always stores 4 bytes regardless of the caller-supplied optlen. The existing min_t(u32, len, sizeof(u32)) only clamps the length reported back to userspace; it does not constrain the store. A call with optlen &lt; 4 therefore writes past the user buffer, violating the getsockopt(2) contract for all five supported optnames.</p> <p>Reject any call with optlen &lt; sizeof(u32) up front. &#39;len&#39; is int, so a plain size comparison would promote a negative optlen to size_t and slip past the check; an explicit &#39;len &lt; 0&#39; test is added first to catch negative values before the size compare.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>nfc: llcp: avoid userspace overflow on invalid optlen</p> <p>nfc_llcp_getsockopt() casts optval to (u32 __user *) for put_user(), so the kernel always stores 4 bytes regardless of the caller-supplied optlen. The existing min_t(u32, len, sizeof(u32)) only clamps the length reported back to userspace; it does not constrain the store. A call with optlen &lt; 4 therefore writes past the user buffer, violating the getsockopt(2) contract for all five supported optnames.</p> <p>Reject any call with optlen &lt; sizeof(u32) up front. &#39;len&#39; is int, so a plain size comparison would promote a negative optlen to size_t and slip past the check; an explicit &#39;len &lt; 0&#39; test is added first to catch negative values before the size compare.</p> https://vulnerability.circl.lu/vuln/fkie_cve-2026-90226 https://vulnerability.circl.lu/vuln/ghsa-phjm-5cmf-7w3f <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>nfc: llcp: avoid userspace overflow on invalid optlen</p> <p>nfc_llcp_getsockopt() casts optval to (u32 __user *) for put_user(), so the kernel always stores 4 bytes regardless of the caller-supplied optlen. The existing min_t(u32, len, sizeof(u32)) only clamps the length reported back to userspace; it does not constrain the store. A call with optlen &lt; 4 therefore writes past the user buffer, violating the getsockopt(2) contract for all five supported optnames.</p> <p>Reject any call with optlen &lt; sizeof(u32) up front. &#39;len&#39; is int, so a plain size comparison would promote a negative optlen to size_t and slip past the check; an explicit &#39;len &lt; 0&#39; test is added first to catch negative values before the size compare.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>nfc: llcp: avoid userspace overflow on invalid optlen</p> <p>nfc_llcp_getsockopt() casts optval to (u32 __user *) for put_user(), so the kernel always stores 4 bytes regardless of the caller-supplied optlen. The existing min_t(u32, len, sizeof(u32)) only clamps the length reported back to userspace; it does not constrain the store. A call with optlen &lt; 4 therefore writes past the user buffer, violating the getsockopt(2) contract for all five supported optnames.</p> <p>Reject any call with optlen &lt; sizeof(u32) up front. &#39;len&#39; is int, so a plain size comparison would promote a negative optlen to size_t and slip past the check; an explicit &#39;len &lt; 0&#39; test is added first to catch negative values before the size compare.</p> https://vulnerability.circl.lu/vuln/ghsa-phjm-5cmf-7w3f https://vulnerability.circl.lu/vuln/msrc_cve-2026-90226 msrc_CVE-2026-90226 https://vulnerability.circl.lu/vuln/msrc_cve-2026-90226 https://vulnerability.circl.lu/vuln/opensuse-su-2026:11880-1 <p>kernel-devel-7.2.7-1.1 on GA media</p> <p>kernel-devel-7.2.7-1.1 on GA media</p> https://vulnerability.circl.lu/vuln/opensuse-su-2026:11880-1 https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-90226 <p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 246 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: nfc: llcp: avoid userspace overflow on invalid optlen nfc_llcp_getsockopt() casts optval to (u32 __user *) for put_user(), so the kernel always stores 4 bytes regardless of the caller-supplied optlen. The existing min_t(u32, len, sizeof(u32)) only clamps the length reported back to userspace; it does not constrain the store. A call with optlen &lt; 4 therefore writes past the user buffer, violating the getsockopt(2) contract for all five supported optnames. Reject any call with optlen &lt; sizeof(u32) up front. &#39;len&#39; is int, so a plain size comparison would promote a negative optlen to size_t and slip past the check; an explicit &#39;len &lt; 0&#39; test is added first to catch negative values before the size compare.</p> <p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 246 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: nfc: llcp: avoid userspace overflow on invalid optlen nfc_llcp_getsockopt() casts optval to (u32 __user *) for put_user(), so the kernel always stores 4 bytes regardless of the caller-supplied optlen. The existing min_t(u32, len, sizeof(u32)) only clamps the length reported back to userspace; it does not constrain the store. A call with optlen &lt; 4 therefore writes past the user buffer, violating the getsockopt(2) contract for all five supported optnames. Reject any call with optlen &lt; sizeof(u32) up front. &#39;len&#39; is int, so a plain size comparison would promote a negative optlen to size_t and slip past the check; an explicit &#39;len &lt; 0&#39; test is added first to catch negative values before the size compare.</p> https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-90226