<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Thu, 15 Oct 2026 19:34:57 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-68758 — backlight: led-bl: Add devlink to supplier LEDs</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2025-68758</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;backlight: led-bl: Add devlink to supplier LEDs&lt;/p&gt;
&lt;p&gt;LED Backlight is a consumer of one or multiple LED class devices, but
devlink is currently unable to create correct supplier-producer links when
the supplier is a class device. It creates instead a link where the
supplier is the parent of the expected device.&lt;/p&gt;
&lt;p&gt;One consequence is that removal order is not correctly enforced.&lt;/p&gt;
&lt;p&gt;Issues happen for example with the following sections in a device tree
overlay:&lt;/p&gt;
&lt;p&gt;// An LED driver chip
    pca9632@62 {
        compatible = &amp;#34;nxp,pca9632&amp;#34;;
        reg = &amp;lt;0x62&amp;gt;;&lt;/p&gt;
&lt;p&gt;// ...&lt;/p&gt;
&lt;p&gt;addon_led_pwm: led-pwm@3 {
            reg = &amp;lt;3&amp;gt;;
            label = &amp;#34;addon:led:pwm&amp;#34;;
        };
    };&lt;/p&gt;
&lt;p&gt;backlight-addon {
        compatible = &amp;#34;led-backlight&amp;#34;;
        leds = &amp;lt;&amp;amp;addon_led_pwm&amp;gt;;
        brightness-levels = &amp;lt;255&amp;gt;;
        default-brightness-level = &amp;lt;255&amp;gt;;
    };&lt;/p&gt;
&lt;p&gt;In this example, the devlink should be created between the backlight-addon
(consumer) and the pca9632@62 (supplier). Instead it is created between the
backlight-addon (consumer) and the parent of the pca9632@62, which is
typically the I2C bus adapter.&lt;/p&gt;
&lt;p&gt;On removal of the above overlay, the LED driver can be removed before the
backlight device, resulting in:&lt;/p&gt;
&lt;p&gt;Unable to handle kernel NULL pointer dereference at virtual address 0000000000000010
    ...
    Call trace:
     led_put+0xe0/0x140
     devm_led_release+0x6c/0x98&lt;/p&gt;
&lt;p&gt;Another way to reproduce the bug without…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;backlight: led-bl: Add devlink to supplier LEDs&lt;/p&gt;
&lt;p&gt;LED Backlight is a consumer of one or multiple LED class devices, but
devlink is currently unable to create correct supplier-producer links when
the supplier is a class device. It creates instead a link where the
supplier is the parent of the expected device.&lt;/p&gt;
&lt;p&gt;One consequence is that removal order is not correctly enforced.&lt;/p&gt;
&lt;p&gt;Issues happen for example with the following sections in a device tree
overlay:&lt;/p&gt;
&lt;p&gt;// An LED driver chip
    pca9632@62 {
        compatible = &amp;#34;nxp,pca9632&amp;#34;;
        reg = &amp;lt;0x62&amp;gt;;&lt;/p&gt;
&lt;p&gt;// ...&lt;/p&gt;
&lt;p&gt;addon_led_pwm: led-pwm@3 {
            reg = &amp;lt;3&amp;gt;;
            label = &amp;#34;addon:led:pwm&amp;#34;;
        };
    };&lt;/p&gt;
&lt;p&gt;backlight-addon {
        compatible = &amp;#34;led-backlight&amp;#34;;
        leds = &amp;lt;&amp;amp;addon_led_pwm&amp;gt;;
        brightness-levels = &amp;lt;255&amp;gt;;
        default-brightness-level = &amp;lt;255&amp;gt;;
    };&lt;/p&gt;
&lt;p&gt;In this example, the devlink should be created between the backlight-addon
(consumer) and the pca9632@62 (supplier). Instead it is created between the
backlight-addon (consumer) and the parent of the pca9632@62, which is
typically the I2C bus adapter.&lt;/p&gt;
&lt;p&gt;On removal of the above overlay, the LED driver can be removed before the
backlight device, resulting in:&lt;/p&gt;
&lt;p&gt;Unable to handle kernel NULL pointer dereference at virtual address 0000000000000010
    ...
    Call trace:
     led_put+0xe0/0x140
     devm_led_release+0x6c/0x98&lt;/p&gt;
&lt;p&gt;Another way to reproduce the bug without…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2025-68758</guid>
    </item>
    <item>
      <title>USN-8094-1 — linux, linux-aws, linux-aws-6.17, linux-gcp, linux-hwe-6.17, linux-oracle, linux-oracle-6.17 vulnerabilities</title>
      <link>https://cve.radiocsirt.org/vuln/usn-8094-1</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:24.04:LTS: linux-aws-6.17, Ubuntu:24.04:LTS: linux-hwe-6.17, Ubuntu:24.04:LTS: linux-oracle-6.17, Ubuntu:25.10: linux, Ubuntu:25.10: linux-aws, Ubuntu:25.10: linux-gcp, Ubuntu:25.10: linux-oracle&lt;/p&gt;
&lt;p&gt;Qualys discovered that several vulnerabilities existed in the AppArmor
Linux kernel Security Module (LSM). An unprivileged local attacker could
use these issues to load, replace, and remove arbitrary AppArmor profiles
causing denial of service, exposure of sensitive information (kernel
memory), local privilege escalation, or possibly escape a container.
(LP: #2143853)&lt;/p&gt;
&lt;p&gt;It was discovered that some AMD Zen 5 processors supporting RDSEED
instruction did not properly handle entropy, potentially resulting in the
consumption of insufficiently random values. A local attacker could
possibly use this issue to influence the values returned by the RDSEED
instruction causing loss of confidentiality and integrity. (CVE-2025-62626)&lt;/p&gt;
&lt;p&gt;Several security issues were discovered in the Linux kernel.
An attacker could possibly use these to compromise the system.
This update corrects flaws in the following subsystems:
  - ARM64 architecture;
  - S390 architecture;
  - x86 architecture;
  - Block layer subsystem;
  - Cryptographic API;
  - Compute Acceleration Framework;
  - ATM drivers;
  - Network block device driver;
  - Bluetooth drivers;
  - Data acquisition framework and drivers;
  - Hardware crypto device drivers;
  - Device frequency scaling framework;
  - Intel Stratix 10 firmware drivers;
  - GPIO subsystem;
  - GPU drivers;
  - Microsoft Hyper-V drivers;
  - CoreSight HW tracing drivers;
  - IIO subsystem;
  - InfiniBand drivers;
  - Input Device core drivers;
  - Input Device (Tablet) d…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:24.04:LTS: linux-aws-6.17, Ubuntu:24.04:LTS: linux-hwe-6.17, Ubuntu:24.04:LTS: linux-oracle-6.17, Ubuntu:25.10: linux, Ubuntu:25.10: linux-aws, Ubuntu:25.10: linux-gcp, Ubuntu:25.10: linux-oracle&lt;/p&gt;
&lt;p&gt;Qualys discovered that several vulnerabilities existed in the AppArmor
Linux kernel Security Module (LSM). An unprivileged local attacker could
use these issues to load, replace, and remove arbitrary AppArmor profiles
causing denial of service, exposure of sensitive information (kernel
memory), local privilege escalation, or possibly escape a container.
(LP: #2143853)&lt;/p&gt;
&lt;p&gt;It was discovered that some AMD Zen 5 processors supporting RDSEED
instruction did not properly handle entropy, potentially resulting in the
consumption of insufficiently random values. A local attacker could
possibly use this issue to influence the values returned by the RDSEED
instruction causing loss of confidentiality and integrity. (CVE-2025-62626)&lt;/p&gt;
&lt;p&gt;Several security issues were discovered in the Linux kernel.
An attacker could possibly use these to compromise the system.
This update corrects flaws in the following subsystems:
  - ARM64 architecture;
  - S390 architecture;
  - x86 architecture;
  - Block layer subsystem;
  - Cryptographic API;
  - Compute Acceleration Framework;
  - ATM drivers;
  - Network block device driver;
  - Bluetooth drivers;
  - Data acquisition framework and drivers;
  - Hardware crypto device drivers;
  - Device frequency scaling framework;
  - Intel Stratix 10 firmware drivers;
  - GPIO subsystem;
  - GPU drivers;
  - Microsoft Hyper-V drivers;
  - CoreSight HW tracing drivers;
  - IIO subsystem;
  - InfiniBand drivers;
  - Input Device core drivers;
  - Input Device (Tablet) d…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/usn-8094-1</guid>
    </item>
  </channel>
</rss>
