<?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://db.gcve.eu</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 21:27:55 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-99638</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-99638</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;net/sched: clamp skb-&amp;gt;queue_mapping before indexing the tx queue&lt;/p&gt;
&lt;p&gt;This issue was caught by Sashiko (nipa). A producer-side path cap is
already merged (ea4d4b5dddb5); this patch adds the matching consumer-side
caps.&lt;/p&gt;
&lt;p&gt;The issue:
The tx queue is picked and capped in netdev_core_pick_tx() before the
__dev_xmit_skb() qdisc enqueue path. A tc BPF program running inside an
egress qdisc (not clsact) can then change __sk_buff-&amp;gt;queue_mapping; that
store is never re-checked. bpf_convert_ctx_access() bounds it only by
NO_QUEUE_MAPPING, not by the device&amp;#39;s queue count.&lt;/p&gt;
&lt;p&gt;Two consumers read the stale value:&lt;/p&gt;
&lt;p&gt;- On dequeue, qdisc_restart() calls netdev_get_tx_queue(), which
    indexes dev-&amp;gt;_tx[]. netdev_get_tx_queue() guards it with just a
    DEBUG_NET_WARN_ON_ONCE, so sch_direct_xmit() takes the out-of-bounds
    txq-&amp;gt;_xmit_lock and writes txq-&amp;gt;xmit_lock_owner past the end of the
    allocation on non-lltx devices such as ifb. Drivers that index their
    rings from skb_get_queue_mapping() (ex: ifb) go out of range the same
    way.&lt;/p&gt;
&lt;p&gt;- On enqueue, taprio_enqueue() indexes q-&amp;gt;qdiscs[] with the same value;
    the array is sized dev-&amp;gt;num_tx_queues. A duplicating netem on a child
    qdisc clones the skb and re-enqueues the clone at the taprio root
    (qdisc_root_bh()) through a direct rootq-&amp;gt;enqueue() call, so the value
    reaches taprio_enqueue() before any dequeue cap runs.&lt;/p&gt;
&lt;p&gt;The Fix:
Cap the mapping at the consumer…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;net/sched: clamp skb-&amp;gt;queue_mapping before indexing the tx queue&lt;/p&gt;
&lt;p&gt;This issue was caught by Sashiko (nipa). A producer-side path cap is
already merged (ea4d4b5dddb5); this patch adds the matching consumer-side
caps.&lt;/p&gt;
&lt;p&gt;The issue:
The tx queue is picked and capped in netdev_core_pick_tx() before the
__dev_xmit_skb() qdisc enqueue path. A tc BPF program running inside an
egress qdisc (not clsact) can then change __sk_buff-&amp;gt;queue_mapping; that
store is never re-checked. bpf_convert_ctx_access() bounds it only by
NO_QUEUE_MAPPING, not by the device&amp;#39;s queue count.&lt;/p&gt;
&lt;p&gt;Two consumers read the stale value:&lt;/p&gt;
&lt;p&gt;- On dequeue, qdisc_restart() calls netdev_get_tx_queue(), which
    indexes dev-&amp;gt;_tx[]. netdev_get_tx_queue() guards it with just a
    DEBUG_NET_WARN_ON_ONCE, so sch_direct_xmit() takes the out-of-bounds
    txq-&amp;gt;_xmit_lock and writes txq-&amp;gt;xmit_lock_owner past the end of the
    allocation on non-lltx devices such as ifb. Drivers that index their
    rings from skb_get_queue_mapping() (ex: ifb) go out of range the same
    way.&lt;/p&gt;
&lt;p&gt;- On enqueue, taprio_enqueue() indexes q-&amp;gt;qdiscs[] with the same value;
    the array is sized dev-&amp;gt;num_tx_queues. A duplicating netem on a child
    qdisc clones the skb and re-enqueues the clone at the taprio root
    (qdisc_root_bh()) through a direct rootq-&amp;gt;enqueue() call, so the value
    reaches taprio_enqueue() before any dequeue cap runs.&lt;/p&gt;
&lt;p&gt;The Fix:
Cap the mapping at the consumer…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-99638</guid>
    </item>
    <item>
      <title>GHSA-mc2m-r8cg-frfw</title>
      <link>https://db.gcve.eu/vuln/ghsa-mc2m-r8cg-frfw</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;net/sched: clamp skb-&amp;gt;queue_mapping before indexing the tx queue&lt;/p&gt;
&lt;p&gt;This issue was caught by Sashiko (nipa). A producer-side path cap is
already merged (ea4d4b5dddb5); this patch adds the matching consumer-side
caps.&lt;/p&gt;
&lt;p&gt;The issue:
The tx queue is picked and capped in netdev_core_pick_tx() before the
__dev_xmit_skb() qdisc enqueue path. A tc BPF program running inside an
egress qdisc (not clsact) can then change __sk_buff-&amp;gt;queue_mapping; that
store is never re-checked. bpf_convert_ctx_access() bounds it only by
NO_QUEUE_MAPPING, not by the device&amp;#39;s queue count.&lt;/p&gt;
&lt;p&gt;Two consumers read the stale value:&lt;/p&gt;
&lt;p&gt;- On dequeue, qdisc_restart() calls netdev_get_tx_queue(), which
    indexes dev-&amp;gt;_tx[]. netdev_get_tx_queue() guards it with just a
    DEBUG_NET_WARN_ON_ONCE, so sch_direct_xmit() takes the out-of-bounds
    txq-&amp;gt;_xmit_lock and writes txq-&amp;gt;xmit_lock_owner past the end of the
    allocation on non-lltx devices such as ifb. Drivers that index their
    rings from skb_get_queue_mapping() (ex: ifb) go out of range the same
    way.&lt;/p&gt;
&lt;p&gt;- On enqueue, taprio_enqueue() indexes q-&amp;gt;qdiscs[] with the same value;
    the array is sized dev-&amp;gt;num_tx_queues. A duplicating netem on a child
    qdisc clones the skb and re-enqueues the clone at the taprio root
    (qdisc_root_bh()) through a direct rootq-&amp;gt;enqueue() call, so the value
    reaches taprio_enqueue() before any dequeue cap runs.&lt;/p&gt;
&lt;p&gt;The Fix:
Cap the mapping at the consumer…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;net/sched: clamp skb-&amp;gt;queue_mapping before indexing the tx queue&lt;/p&gt;
&lt;p&gt;This issue was caught by Sashiko (nipa). A producer-side path cap is
already merged (ea4d4b5dddb5); this patch adds the matching consumer-side
caps.&lt;/p&gt;
&lt;p&gt;The issue:
The tx queue is picked and capped in netdev_core_pick_tx() before the
__dev_xmit_skb() qdisc enqueue path. A tc BPF program running inside an
egress qdisc (not clsact) can then change __sk_buff-&amp;gt;queue_mapping; that
store is never re-checked. bpf_convert_ctx_access() bounds it only by
NO_QUEUE_MAPPING, not by the device&amp;#39;s queue count.&lt;/p&gt;
&lt;p&gt;Two consumers read the stale value:&lt;/p&gt;
&lt;p&gt;- On dequeue, qdisc_restart() calls netdev_get_tx_queue(), which
    indexes dev-&amp;gt;_tx[]. netdev_get_tx_queue() guards it with just a
    DEBUG_NET_WARN_ON_ONCE, so sch_direct_xmit() takes the out-of-bounds
    txq-&amp;gt;_xmit_lock and writes txq-&amp;gt;xmit_lock_owner past the end of the
    allocation on non-lltx devices such as ifb. Drivers that index their
    rings from skb_get_queue_mapping() (ex: ifb) go out of range the same
    way.&lt;/p&gt;
&lt;p&gt;- On enqueue, taprio_enqueue() indexes q-&amp;gt;qdiscs[] with the same value;
    the array is sized dev-&amp;gt;num_tx_queues. A duplicating netem on a child
    qdisc clones the skb and re-enqueues the clone at the taprio root
    (qdisc_root_bh()) through a direct rootq-&amp;gt;enqueue() call, so the value
    reaches taprio_enqueue() before any dequeue cap runs.&lt;/p&gt;
&lt;p&gt;The Fix:
Cap the mapping at the consumer…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-mc2m-r8cg-frfw</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-4695 — Linux Kernel: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff</title>
      <link>https://db.gcve.eu/vuln/wid-sec-w-2026-4695</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise einen Denial-of-Service-Angriff auszulösen, Daten zu manipulieren oder offenzulegen oder Sicherheitsmaßnahmen zu umgehen&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise einen Denial-of-Service-Angriff auszulösen, Daten zu manipulieren oder offenzulegen oder Sicherheitsmaßnahmen zu umgehen&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/wid-sec-w-2026-4695</guid>
    </item>
  </channel>
</rss>
