<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://127.0.0.1:10001/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-11-21T07:08:31.384994+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://127.0.0.1:10001" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://127.0.0.1:10001/vuln/bell-cve-2026-46081</id>
    <title>BELL-CVE-2026-46081</title>
    <updated>2026-11-21T07:08:31.394808+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p><strong>Affected:</strong> Alpaquita:stream: linux-lts</p>
      </div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/bell-cve-2026-46081"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/certfr-2026-avi-0831</id>
    <title>certfr-2026-avi-0831 — De multiples vulnérabilités ont été découvertes dans le noyau Linux d'Ubuntu. Certaines d'entre elles permettent à un a…</title>
    <updated>2026-11-21T07:08:31.394892+00:00</updated>
    <content>certfr-2026-avi-0831</content>
    <link href="https://127.0.0.1:10001/vuln/certfr-2026-avi-0831"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/ubuntu-cve-2026-46081</id>
    <title>UBUNTU-CVE-2026-46081</title>
    <updated>2026-11-21T07:08:31.394916+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><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 116 more</p>
<p>In the Linux kernel, the following vulnerability has been resolved: crypto: acomp - fix wrong pointer stored by acomp_save_req() acomp_save_req() stores &amp;req-&gt;chain in req-&gt;base.data. When acomp_reqchain_done() is invoked on asynchronous completion, it receives &amp;req-&gt;chain as the data argument but casts it directly to struct acomp_req. Since data points to the chain member, all subsequent field accesses are at a wrong offset, resulting in memory corruption. The issue occurs when an asynchronous hardware implementation, such as the QAT driver, completes a request that uses the DMA virtual address interface (e.g. acomp_request_set_src_dma()). This combination causes crypto_acomp_compress() to enter the acomp_do_req_chain() path, which sets acomp_reqchain_done() as the completion callback via acomp_save_req(). With KASAN enabled, this manifests as a general protection fault in acomp_reqchain_done():   general protection fault, probably for non-canonical address 0xe000040000000000   KASAN: probably user-memory-access in range [0x0000400000000000-0x0000400000000007]   RIP: 0010:acomp_reqchain_done+0x15b/0x4e0   Call Trace:    &lt;IRQ&gt;    qat_comp_alg_callback+0x5d/0xa0 [intel_qat]    adf_ring_response_handler+0x376/0x8b0 [intel_qat]    adf_response_handler+0x60/0x170 [intel_qat]    tasklet_action_common+0x223/0x820    handle_softirqs+0x1ab/0x640    &lt;/IRQ&gt; Fix this by storing the request itself in req-&gt;base.data instead of &amp;req-&gt;chain, so that acomp_reqchain_done() receives the corre…</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/ubuntu-cve-2026-46081"/>
  </entry>
</feed>
