<?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://127.0.0.1:10001</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>Sat, 21 Nov 2026 06:41:15 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2024-44960</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2024-44960</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/bell-cve-2024-44960</guid>
    </item>
    <item>
      <title>certfr-2024-avi-0870 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de SUSE. Certaines d'entre elles permettent à un at…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2024-avi-0870</link>
      <description>certfr-2024-avi-0870</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2024-avi-0870</guid>
    </item>
    <item>
      <title>OESA-2024-2150 — kernel security update</title>
      <link>https://127.0.0.1:10001/vuln/oesa-2024-2150</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.03-LTS-SP4: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
media: aspeed: Fix memory overwrite if timing is 1600x900&#13;
&#13;
When capturing 1600x900, system could crash when system memory usage is
tight.&#13;
&#13;
The way to reproduce this issue:
1. Use 1600x900 to display on host
2. Mount ISO through &amp;amp;apos;Virtual media&amp;amp;apos; on OpenBMC&amp;amp;apos;s web
3. Run script as below on host to do sha continuously
  #!/bin/bash
  while [ [1] ];
  do
	find /media -type f -printf &amp;amp;apos;&amp;amp;quot;%h/%f&amp;amp;quot;\n&amp;amp;apos; | xargs sha256sum
  done
4. Open KVM on OpenBMC&amp;amp;apos;s web&#13;
&#13;
The size of macro block captured is 8x8. Therefore, we should make sure
the height of src-buf is 8 aligned to fix this issue.(CVE-2023-52916)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
drm/qxl: Add check for drm_cvt_mode&#13;
&#13;
Add check for the return value of drm_cvt_mode() and return the error if
it fails in order to avoid NULL pointer dereference.(CVE-2024-43829)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
usb: gadget: core: Check for unset descriptor&#13;
&#13;
Make sure the descriptor has been set before looking at maxpacket.
This fixes a null pointer panic in this case.&#13;
&#13;
This may happen if the gadget doesn&amp;amp;apos;t properly set up the endpoint
for the current speed, or the gadget descriptors are malformed and
the descriptor for the speed/endpoint are not found.&#13;
&#13;
No current gadget driver is…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.03-LTS-SP4: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
media: aspeed: Fix memory overwrite if timing is 1600x900&#13;
&#13;
When capturing 1600x900, system could crash when system memory usage is
tight.&#13;
&#13;
The way to reproduce this issue:
1. Use 1600x900 to display on host
2. Mount ISO through &amp;amp;apos;Virtual media&amp;amp;apos; on OpenBMC&amp;amp;apos;s web
3. Run script as below on host to do sha continuously
  #!/bin/bash
  while [ [1] ];
  do
	find /media -type f -printf &amp;amp;apos;&amp;amp;quot;%h/%f&amp;amp;quot;\n&amp;amp;apos; | xargs sha256sum
  done
4. Open KVM on OpenBMC&amp;amp;apos;s web&#13;
&#13;
The size of macro block captured is 8x8. Therefore, we should make sure
the height of src-buf is 8 aligned to fix this issue.(CVE-2023-52916)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
drm/qxl: Add check for drm_cvt_mode&#13;
&#13;
Add check for the return value of drm_cvt_mode() and return the error if
it fails in order to avoid NULL pointer dereference.(CVE-2024-43829)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
usb: gadget: core: Check for unset descriptor&#13;
&#13;
Make sure the descriptor has been set before looking at maxpacket.
This fixes a null pointer panic in this case.&#13;
&#13;
This may happen if the gadget doesn&amp;amp;apos;t properly set up the endpoint
for the current speed, or the gadget descriptors are malformed and
the descriptor for the speed/endpoint are not found.&#13;
&#13;
No current gadget driver is…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/oesa-2024-2150</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-44960</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2024-44960</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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, Ubuntu:16.04:LTS: linux-hwe-edge and 182 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: usb: gadget: core: Check for unset descriptor Make sure the descriptor has been set before looking at maxpacket. This fixes a null pointer panic in this case. This may happen if the gadget doesn&amp;#39;t properly set up the endpoint for the current speed, or the gadget descriptors are malformed and the descriptor for the speed/endpoint are not found. No current gadget driver is known to have this problem, but this may cause a hard-to-find bug during development of new gadgets.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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, Ubuntu:16.04:LTS: linux-hwe-edge and 182 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: usb: gadget: core: Check for unset descriptor Make sure the descriptor has been set before looking at maxpacket. This fixes a null pointer panic in this case. This may happen if the gadget doesn&amp;#39;t properly set up the endpoint for the current speed, or the gadget descriptors are malformed and the descriptor for the speed/endpoint are not found. No current gadget driver is known to have this problem, but this may cause a hard-to-find bug during development of new gadgets.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2024-44960</guid>
    </item>
  </channel>
</rss>
