https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sun, 04 Oct 2026 13:54:32 +0000 https://cve.radiocsirt.org/vuln/bdu:2025-11764 bdu:2025-11764 https://cve.radiocsirt.org/vuln/bdu:2025-11764 https://cve.radiocsirt.org/vuln/bell-cve-2025-38027 <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://cve.radiocsirt.org/vuln/bell-cve-2025-38027 https://cve.radiocsirt.org/vuln/certfr-2025-avi-0587 certfr-2025-avi-0587 https://cve.radiocsirt.org/vuln/certfr-2025-avi-0587 https://cve.radiocsirt.org/vuln/euvd-2026-314382 EUVD-2026-314382 https://cve.radiocsirt.org/vuln/euvd-2026-314382 https://cve.radiocsirt.org/vuln/fkie_cve-2025-38027 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>regulator: max20086: fix invalid memory access</p> <p>max20086_parse_regulators_dt() calls of_regulator_match() using an array of struct of_regulator_match allocated on the stack for the matches argument.</p> <p>of_regulator_match() calls devm_of_regulator_put_matches(), which calls devres_alloc() to allocate a struct devm_of_regulator_matches which will be de-allocated using devm_of_regulator_put_matches().</p> <p>struct devm_of_regulator_matches is populated with the stack allocated matches array.</p> <p>If the device fails to probe, devm_of_regulator_put_matches() will be called and will try to call of_node_put() on that stack pointer, generating the following dmesg entries:</p> <p>max20086 6-0028: Failed to read DEVICE_ID reg: -121 kobject: &#39;\xc0$\xa5\x03&#39; (000000002cebcb7a): is not initialized, yet kobject_put() is being called.</p> <p>Followed by a stack trace matching the call flow described above.</p> <p>Switch to allocating the matches array using devm_kcalloc() to avoid accessing the stack pointer long after it&#39;s out of scope.</p> <p>This also has the advantage of allowing multiple max20086 to probe without overriding the data stored inside the global of_regulator_match.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>regulator: max20086: fix invalid memory access</p> <p>max20086_parse_regulators_dt() calls of_regulator_match() using an array of struct of_regulator_match allocated on the stack for the matches argument.</p> <p>of_regulator_match() calls devm_of_regulator_put_matches(), which calls devres_alloc() to allocate a struct devm_of_regulator_matches which will be de-allocated using devm_of_regulator_put_matches().</p> <p>struct devm_of_regulator_matches is populated with the stack allocated matches array.</p> <p>If the device fails to probe, devm_of_regulator_put_matches() will be called and will try to call of_node_put() on that stack pointer, generating the following dmesg entries:</p> <p>max20086 6-0028: Failed to read DEVICE_ID reg: -121 kobject: &#39;\xc0$\xa5\x03&#39; (000000002cebcb7a): is not initialized, yet kobject_put() is being called.</p> <p>Followed by a stack trace matching the call flow described above.</p> <p>Switch to allocating the matches array using devm_kcalloc() to avoid accessing the stack pointer long after it&#39;s out of scope.</p> <p>This also has the advantage of allowing multiple max20086 to probe without overriding the data stored inside the global of_regulator_match.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2025-38027 https://cve.radiocsirt.org/vuln/ghsa-53c4-pm56-gg9x <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>regulator: max20086: fix invalid memory access</p> <p>max20086_parse_regulators_dt() calls of_regulator_match() using an array of struct of_regulator_match allocated on the stack for the matches argument.</p> <p>of_regulator_match() calls devm_of_regulator_put_matches(), which calls devres_alloc() to allocate a struct devm_of_regulator_matches which will be de-allocated using devm_of_regulator_put_matches().</p> <p>struct devm_of_regulator_matches is populated with the stack allocated matches array.</p> <p>If the device fails to probe, devm_of_regulator_put_matches() will be called and will try to call of_node_put() on that stack pointer, generating the following dmesg entries:</p> <p>max20086 6-0028: Failed to read DEVICE_ID reg: -121 kobject: &#39;\xc0$\xa5\x03&#39; (000000002cebcb7a): is not initialized, yet kobject_put() is being called.</p> <p>Followed by a stack trace matching the call flow described above.</p> <p>Switch to allocating the matches array using devm_kcalloc() to avoid accessing the stack pointer long after it&#39;s out of scope.</p> <p>This also has the advantage of allowing multiple max20086 to probe without overriding the data stored inside the global of_regulator_match.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>regulator: max20086: fix invalid memory access</p> <p>max20086_parse_regulators_dt() calls of_regulator_match() using an array of struct of_regulator_match allocated on the stack for the matches argument.</p> <p>of_regulator_match() calls devm_of_regulator_put_matches(), which calls devres_alloc() to allocate a struct devm_of_regulator_matches which will be de-allocated using devm_of_regulator_put_matches().</p> <p>struct devm_of_regulator_matches is populated with the stack allocated matches array.</p> <p>If the device fails to probe, devm_of_regulator_put_matches() will be called and will try to call of_node_put() on that stack pointer, generating the following dmesg entries:</p> <p>max20086 6-0028: Failed to read DEVICE_ID reg: -121 kobject: &#39;\xc0$\xa5\x03&#39; (000000002cebcb7a): is not initialized, yet kobject_put() is being called.</p> <p>Followed by a stack trace matching the call flow described above.</p> <p>Switch to allocating the matches array using devm_kcalloc() to avoid accessing the stack pointer long after it&#39;s out of scope.</p> <p>This also has the advantage of allowing multiple max20086 to probe without overriding the data stored inside the global of_regulator_match.</p> https://cve.radiocsirt.org/vuln/ghsa-53c4-pm56-gg9x https://cve.radiocsirt.org/vuln/suse-su-2025:02249-1 <p>Security update for the Linux Kernel</p> <p>Security update for the Linux Kernel</p> https://cve.radiocsirt.org/vuln/suse-su-2025:02249-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-38027 <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 120 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: regulator: max20086: fix invalid memory access max20086_parse_regulators_dt() calls of_regulator_match() using an array of struct of_regulator_match allocated on the stack for the matches argument. of_regulator_match() calls devm_of_regulator_put_matches(), which calls devres_alloc() to allocate a struct devm_of_regulator_matches which will be de-allocated using devm_of_regulator_put_matches(). struct devm_of_regulator_matches is populated with the stack allocated matches array. If the device fails to probe, devm_of_regulator_put_matches() will be called and will try to call of_node_put() on that stack pointer, generating the following dmesg entries: max20086 6-0028: Failed to read DEVICE_ID reg: -121 kobject: &#39;\xc0$\xa5\x03&#39; (000000002cebcb7a): is not initialized, yet kobject_put() is being called. Followed by a stack trace matching the call flow described above. Switch to allocating the matches array using devm_kcalloc() to avoid accessing the stack pointer long after it&#39;s out of scope. This also has the advantage of allowing multiple max20086 to probe without overriding the data stored inside the global of_regulator_match.</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 120 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: regulator: max20086: fix invalid memory access max20086_parse_regulators_dt() calls of_regulator_match() using an array of struct of_regulator_match allocated on the stack for the matches argument. of_regulator_match() calls devm_of_regulator_put_matches(), which calls devres_alloc() to allocate a struct devm_of_regulator_matches which will be de-allocated using devm_of_regulator_put_matches(). struct devm_of_regulator_matches is populated with the stack allocated matches array. If the device fails to probe, devm_of_regulator_put_matches() will be called and will try to call of_node_put() on that stack pointer, generating the following dmesg entries: max20086 6-0028: Failed to read DEVICE_ID reg: -121 kobject: &#39;\xc0$\xa5\x03&#39; (000000002cebcb7a): is not initialized, yet kobject_put() is being called. Followed by a stack trace matching the call flow described above. Switch to allocating the matches array using devm_kcalloc() to avoid accessing the stack pointer long after it&#39;s out of scope. This also has the advantage of allowing multiple max20086 to probe without overriding the data stored inside the global of_regulator_match.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-38027 https://cve.radiocsirt.org/vuln/wid-sec-w-2025-1350 <p>Ein lokaler Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen.</p> <p>Ein lokaler Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2025-1350