https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Thu, 01 Oct 2026 05:18:49 +0000 https://vulnerability.circl.lu/vuln/cve-2025-39716 <p><strong>Affected:</strong> Linux, Siemens SIMATIC CN 4100</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>parisc: Revise __get_user() to probe user read access</p> <p>Because of the way read access support is implemented, read access interruptions are only triggered at privilege levels 2 and 3. The kernel executes at privilege level 0, so __get_user() never triggers a read access interruption (code 26). Thus, it is currently possible for user code to access a read protected address via a system call.</p> <p>Fix this by probing read access rights at privilege level 3 (PRIV_USER) and setting __gu_err to -EFAULT (-14) if access isn&#39;t allowed.</p> <p>Note the cmpiclr instruction does a 32-bit compare because COND macro doesn&#39;t work inside asm.</p> <p><strong>Affected:</strong> Linux, Siemens SIMATIC CN 4100</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>parisc: Revise __get_user() to probe user read access</p> <p>Because of the way read access support is implemented, read access interruptions are only triggered at privilege levels 2 and 3. The kernel executes at privilege level 0, so __get_user() never triggers a read access interruption (code 26). Thus, it is currently possible for user code to access a read protected address via a system call.</p> <p>Fix this by probing read access rights at privilege level 3 (PRIV_USER) and setting __gu_err to -EFAULT (-14) if access isn&#39;t allowed.</p> <p>Note the cmpiclr instruction does a 32-bit compare because COND macro doesn&#39;t work inside asm.</p> https://vulnerability.circl.lu/vuln/cve-2025-39716