<?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>Fri, 20 Nov 2026 23:46:01 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2024-49944</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2024-49944</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-49944</guid>
    </item>
    <item>
      <title>certfr-2024-avi-1101 — De multiples vulnérabilités ont été découvertes dans le noyau Linux d'Ubuntu. Certaines d'entre elles permettent à un a…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2024-avi-1101</link>
      <description>certfr-2024-avi-1101</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2024-avi-1101</guid>
    </item>
    <item>
      <title>OESA-2024-2518 — kernel security update</title>
      <link>https://127.0.0.1:10001/vuln/oesa-2024-2518</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;
serial: sc16is7xx: fix invalid FIFO access with special register set&#13;
&#13;
When enabling access to the special register set, Receiver time-out and
RHR interrupts can happen. In this case, the IRQ handler will try to read
from the FIFO thru the RHR register at address 0x00, but address 0x00 is
mapped to DLL register, resulting in erroneous FIFO reading.&#13;
&#13;
Call graph example:
    sc16is7xx_startup(): entry
    sc16is7xx_ms_proc(): entry
    sc16is7xx_set_termios(): entry
    sc16is7xx_set_baud(): DLH/DLL = $009C --&amp;amp;gt; access special register set
    sc16is7xx_port_irq() entry            --&amp;amp;gt; IIR is 0x0C
    sc16is7xx_handle_rx() entry
    sc16is7xx_fifo_read(): --&amp;amp;gt; unable to access FIFO (RHR) because it is
                               mapped to DLL (LCR=LCR_CONF_MODE_A)
    sc16is7xx_set_baud(): exit --&amp;amp;gt; Restore access to general register set&#13;
&#13;
Fix the problem by claiming the efr_lock mutex when accessing the Special
register set.(CVE-2024-44950)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
drm/amd/display: Check link_index before accessing dc-&amp;amp;gt;links[]&#13;
&#13;
[WHY &amp;amp;amp; HOW]
dc-&amp;amp;gt;links[] has max size of MAX_LINKS and NULL is return when trying to
access with out-of-bound index.&#13;
&#13;
This fixes 3 OVERRUN and 1 RESOURCE_LEAK issues reported by Coverity.(CVE-2024-46813)&#13;
&#13;
In the Linux kernel, the…&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;
serial: sc16is7xx: fix invalid FIFO access with special register set&#13;
&#13;
When enabling access to the special register set, Receiver time-out and
RHR interrupts can happen. In this case, the IRQ handler will try to read
from the FIFO thru the RHR register at address 0x00, but address 0x00 is
mapped to DLL register, resulting in erroneous FIFO reading.&#13;
&#13;
Call graph example:
    sc16is7xx_startup(): entry
    sc16is7xx_ms_proc(): entry
    sc16is7xx_set_termios(): entry
    sc16is7xx_set_baud(): DLH/DLL = $009C --&amp;amp;gt; access special register set
    sc16is7xx_port_irq() entry            --&amp;amp;gt; IIR is 0x0C
    sc16is7xx_handle_rx() entry
    sc16is7xx_fifo_read(): --&amp;amp;gt; unable to access FIFO (RHR) because it is
                               mapped to DLL (LCR=LCR_CONF_MODE_A)
    sc16is7xx_set_baud(): exit --&amp;amp;gt; Restore access to general register set&#13;
&#13;
Fix the problem by claiming the efr_lock mutex when accessing the Special
register set.(CVE-2024-44950)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
drm/amd/display: Check link_index before accessing dc-&amp;amp;gt;links[]&#13;
&#13;
[WHY &amp;amp;amp; HOW]
dc-&amp;amp;gt;links[] has max size of MAX_LINKS and NULL is return when trying to
access with out-of-bound index.&#13;
&#13;
This fixes 3 OVERRUN and 1 RESOURCE_LEAK issues reported by Coverity.(CVE-2024-46813)&#13;
&#13;
In the Linux kernel, the…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/oesa-2024-2518</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-49944</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2024-49944</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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 193 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: sctp: set sk_state back to CLOSED if autobind fails in sctp_listen_start In sctp_listen_start() invoked by sctp_inet_listen(), it should set the sk_state back to CLOSED if sctp_autobind() fails due to whatever reason. Otherwise, next time when calling sctp_inet_listen(), if sctp_sk(sk)-&amp;gt;reuse is already set via setsockopt(SCTP_REUSE_PORT), sctp_sk(sk)-&amp;gt;bind_hash will be dereferenced as sk_state is LISTENING, which causes a crash as bind_hash is NULL.   KASAN: null-ptr-deref in range [0x0000000000000000-0x0000000000000007]   RIP: 0010:sctp_inet_listen+0x7f0/0xa20 net/sctp/socket.c:8617   Call Trace:    &amp;lt;TASK&amp;gt;    __sys_listen_socket net/socket.c:1883 [inline]    __sys_listen+0x1b7/0x230 net/socket.c:1894    __do_sys_listen net/socket.c:1902 [inline]&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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 193 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: sctp: set sk_state back to CLOSED if autobind fails in sctp_listen_start In sctp_listen_start() invoked by sctp_inet_listen(), it should set the sk_state back to CLOSED if sctp_autobind() fails due to whatever reason. Otherwise, next time when calling sctp_inet_listen(), if sctp_sk(sk)-&amp;gt;reuse is already set via setsockopt(SCTP_REUSE_PORT), sctp_sk(sk)-&amp;gt;bind_hash will be dereferenced as sk_state is LISTENING, which causes a crash as bind_hash is NULL.   KASAN: null-ptr-deref in range [0x0000000000000000-0x0000000000000007]   RIP: 0010:sctp_inet_listen+0x7f0/0xa20 net/sctp/socket.c:8617   Call Trace:    &amp;lt;TASK&amp;gt;    __sys_listen_socket net/socket.c:1883 [inline]    __sys_listen+0x1b7/0x230 net/socket.c:1894    __do_sys_listen net/socket.c:1902 [inline]&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2024-49944</guid>
    </item>
  </channel>
</rss>
