<?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://db.gcve.eu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-17T18:36:19.429164+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@gcve.eu</email>
  </author>
  <link href="https://db.gcve.eu" 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://db.gcve.eu/vuln/fkie_cve-2026-98383</id>
    <title>fkie_cve-2026-98383</title>
    <updated>2026-10-17T18:36:19.472824+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>bpf: Disallow bpf_skb_pull_data() for LWT_SEG6LOCAL</p>
<p>An LWT_SEG6LOCAL program can invalidate its cached SRH with
bpf_lwt_seg6_adjust_srh() and then call bpf_skb_pull_data(). The latter
may reallocate skb-&gt;head, leaving the per-CPU SRH pointer dangling.
Post-program SRH validation then writes through that pointer.</p>
<p>Disallow bpf_skb_pull_data() for LWT_SEG6LOCAL programs so the verifier
rejects this unsafe helper combination. Other LWT program types continue
to expose the helper through lwt_out_func_proto().</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/fkie_cve-2026-98383"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/ghsa-ph4x-4wh2-2qrm</id>
    <title>GHSA-ph4x-4wh2-2qrm</title>
    <updated>2026-10-17T18:36:19.472902+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>bpf: Disallow bpf_skb_pull_data() for LWT_SEG6LOCAL</p>
<p>An LWT_SEG6LOCAL program can invalidate its cached SRH with
bpf_lwt_seg6_adjust_srh() and then call bpf_skb_pull_data(). The latter
may reallocate skb-&gt;head, leaving the per-CPU SRH pointer dangling.
Post-program SRH validation then writes through that pointer.</p>
<p>Disallow bpf_skb_pull_data() for LWT_SEG6LOCAL programs so the verifier
rejects this unsafe helper combination. Other LWT program types continue
to expose the helper through lwt_out_func_proto().</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/ghsa-ph4x-4wh2-2qrm"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/msrc_cve-2026-98383</id>
    <title>msrc_CVE-2026-98383 — bpf: Disallow bpf_skb_pull_data() for LWT_SEG6LOCAL</title>
    <updated>2026-10-17T18:36:19.472929+00:00</updated>
    <content>msrc_CVE-2026-98383</content>
    <link href="https://db.gcve.eu/vuln/msrc_cve-2026-98383"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/opensuse-su-2026:12131-1</id>
    <title>openSUSE-SU-2026:12131-1 — kernel-devel-7.2.10-1.1 on GA media</title>
    <updated>2026-10-17T18:36:19.472950+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>kernel-devel-7.2.10-1.1 on GA media</p>
      </div>
    </content>
    <link href="https://db.gcve.eu/vuln/opensuse-su-2026:12131-1"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/ubuntu-cve-2026-98383</id>
    <title>UBUNTU-CVE-2026-98383</title>
    <updated>2026-10-17T18:36:19.473054+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:Pro:18.04:LTS: linux-aws-5.4, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:Pro:18.04:LTS: linux-azure-5.4, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3 and 220 more</p>
<p>In the Linux kernel, the following vulnerability has been resolved: bpf: Disallow bpf_skb_pull_data() for LWT_SEG6LOCAL An LWT_SEG6LOCAL program can invalidate its cached SRH with bpf_lwt_seg6_adjust_srh() and then call bpf_skb_pull_data(). The latter may reallocate skb-&gt;head, leaving the per-CPU SRH pointer dangling. Post-program SRH validation then writes through that pointer. Disallow bpf_skb_pull_data() for LWT_SEG6LOCAL programs so the verifier rejects this unsafe helper combination. Other LWT program types continue to expose the helper through lwt_out_func_proto().</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/ubuntu-cve-2026-98383"/>
  </entry>
</feed>
