In the Linux kernel, the following vulnerability has been resolved:
net/sched: clamp skb->queue_mapping before indexing the tx queue
This issue was caught by Sashiko (nipa). A producer-side path cap is
already merged (ea4d4b5dddb5); this patch adds the matching consumer-side
caps.
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->queue_mapping; that
store is never re-checked. bpf_convert_ctx_access() bounds it only by
NO_QUEUE_MAPPING, not by the device's queue count.
Two consumers read the stale value:
- On dequeue, qdisc_restart() calls netdev_get_tx_queue(), which
indexes dev->_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->_xmit_lock and writes txq->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.
- On enqueue, taprio_enqueue() indexes q->qdiscs[] with the same value;
the array is sized dev->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->enqueue() call, so the value
reaches taprio_enqueue() before any dequeue cap runs.
The Fix:
Cap the mapping at the consumers and write the capped value back, so the
qdisc's _tx[] lookup, the taprio q->qdiscs[] lookup and any later driver
read stay in range.
On the dequeue side the cap folds into the dequeue path instead of a
separate walk over the returned list: dequeue_skb() caps the head, and
each bulk helper caps the element it appends. For a qdisc that is not
TCQ_F_ONETXQUEUE, netdev_cap_txqueue() logs a ratelimited notice and
selects queue 0.
A TCQ_F_ONETXQUEUE qdisc is bound to a single tx queue: dequeue_skb() uses
q->dev_queue for the frozen check, the BQL limit and the trace point, while
qdisc_restart() transmits on the skb's queue. Capping an out-of-range
mapping to queue 0 would therefore send a per-queue child's skb through a
different queue than the one it was dequeued for. On mq, mqprio, taprio and
htb offload children, a stopped queue 0 could then park the list in
q->gso_skb, and the later wake would schedule queue 0's own child instead
of this qdisc. Pin a TCQ_F_ONETXQUEUE mapping to the qdisc's own queue to
keep the documented invariant.
The pin covers every mapping, not only an out-of-range one: an in-range
mapping that a filter sets on one of those per-queue children is rewritten
to the child's own queue, and this path does not call netdev_cap_txqueue(),
so it logs no notice. On a single-queue device qdisc_create() sets
TCQ_F_ONETXQUEUE, so the one-queue trigger described below also takes this
branch and is corrected without a notice.
That also keeps a bulk list on one queue by construction: every element of
a TCQ_F_ONETXQUEUE qdisc, including a follower changed by a filter, is
pinned to q->dev_queue before it is appended. The fast bulk helper
therefore needs no head comparison and no skb_bad_txq requeue; the slow
helper, used only by non-ONETXQUEUE qdiscs, still compares and requeues a
mismatched follower, where a wake on any queue reschedules q.
On the enqueue side taprio_enqueue() caps the mapping against
real_num_tx_queues and writes it back before selecting q->qdiscs[queue], so
a duplicating child cannot steer the clone out of the array.
Conditions to recreate the bug:
The dequeue path: load a SCHED_CLS or SCHED_ACT program that stores
__sk_buff->queue_mapping (a tc BPF action is enough), attach it to a
transmit qdisc (for example a matchall filter on a prio root), and send a
packet. With a 1-queue device a store of 1 indexes one past dev->_tx[].
Under KASAN with panic_on_warn=1 the unfixed kernel faults with "BUG:
KASAN: slab-out-
---truncated---
Your early warning system for new security vulnerabilities
Open BETA
Every day brings a flood of new vulnerabilities, roughly 100 CVEs daily. Which one will really affect you?
Attacks on known but unpatched vulnerabilities (Common Vulnerabilities and Exposures, or CVEs for short) are among the most common entry points for hackers. Companies must continuously check for such vulnerabilities. Does this affect our products? Which versions are affected? How critical is it?
As the window between publication and exploitation by attackers keeps shrinking, companies are under more pressure than ever to find a high-quality solution for managing these risks as quickly as possible. However, IT teams are heavily time-constrained, making manual tracking of all relevant CVEs nearly impossible.
100+ new CVEs per day
Most CVEs are irrelevant to your infrastructure
Time-to-exploit < 5 days
Attackers are exploiting vulnerabilities faster than ever before
Manual research is time-consuming
Vendor websites, RSS feeds, and blogs need to be searched daily
Vulnerability scanners are lagging behind
Plugin development isn't progressing fast enough to identify risks in a timely manner
CVE Alarm provides you with immediate notifications of relevant security vulnerabilities
CVE Alarm continuously monitors all newly published CVEs and automatically compares them with the products you use. You will only be notified if a relevant vulnerability affects your systems and meets your defined criteria.
Real-time notification
Direct email notification without delay
Product-based filters
Only CVEs that actually affect your infrastructure
Custom criteria
Filter by CVSS-Score, exposure, products, and vendors
Team-oriented & multi-tenant capable
Assign products or alerts to specific teams or customers
More time to act
Administrators can review and install updates faster
Time savings
No more manually reviewing the flood of new CVE information
Three steps for better patch planning
With CVE Alarm you will easily receive relevant security alerts for your infrastructure.
Subscribe To Products
Select the IT products you use. From Apache to VMware – all critical assets are monitored.
Define Criteria
Set product-specific filters based on criticality (CVSS ≥ 7.0 (high)). You will only receive relevant alerts.
Get Notified
Receive an immediate notification as soon as a matching CVE appears. Recipients can be defined individually for each product.
Be faster than the attackers
With CVE information, you have more time for patch planning and can close security gaps before they are exploited.
Designed for the target group companies and service providers
Whether a global Security Operations Center or a small IT team, CVE Alarm supports CVE monitoring for organizations of all sizes.
Companies with their own IT infrastructure
Medium-sized to large companies that need to proactively monitor their vulnerabilities
Administrators
IT professionals responsible for infrastructure security and maintenance
Security teams and cybersecurity experts
Security Operations Centers (SOCs) and Computer Emergency Response Teams (CERTs) that require CVE information for proactive security measures
Chief Information Security Officers (CISOs) & IT managers
Decision-makers who need an overview of critical vulnerabilities
Security service providers
Managed service providers (MSPs) and security consultancies that manage multiple clients and need to monitor CVEs
From experience to innovation. About us and CVE Alarm.
CVE Alarm is a product of AVABIS GmbH and was developed in collaboration with IT security experts.
AVABIS GmbH – Who are we? We, AVABIS GmbH, are an experienced partner for IT quality assurance. Our focus is on software testing and software development. Our clients, corporations from various industries, have trusted us for more than ten years.
CVE Alarm – How did the idea come about? In our daily project work, we repeatedly witnessed the significant uncertainty surrounding new security alerts. We saw how much time teams have to invest to determine whether a published vulnerability even affects their own system landscape. Based on these experiences, we know how time-consuming it is to gather, evaluate, and prioritize information from diverse sources under time pressure.
This made us realize that the real problem is not a lack of information, but rather an overabundance of it.
This led to the idea of developing a product that enables companies to manage this information overload and maintain control over their IT security.
Developed and operated in Germany Our systems run on German IT infrastructure, and we adhere to high security and data protection standards. This ensures data sovereignty, clear responsibilities, and reliability, especially for organizations with their own security teams or CERT structures.
Get in contact with our team
Do you have questions about CVE Alarm or would you like a personal consultation? We're happy to help.
Please use our contact form.
An error occurred while processing the form, please check your entries.
Thank you for getting in contact with our company
We have received your message and looking forward to speaking with you. We will get back to you personally as soon as possible.