From: Stephen Hemminger <stephen@networkplumber.org>
To: cheung wall <zzqq0103.hey@gmail.com>
Cc: hadi@cyberus.ca, "David S. Miller" <davem@davemloft.net>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: "Bug in qdisc_create" in Linux kernel version 2.6.26
Date: Sun, 1 Dec 2024 21:27:47 -0800 [thread overview]
Message-ID: <20241201212747.13b37633@hermes.local> (raw)
In-Reply-To: <CAKHoSAtJSK6tYjZ8djK27LVuPvAVC=r+Hziv2oxA7vAYZw+30w@mail.gmail.com>
On Mon, 2 Dec 2024 12:31:00 +0800
cheung wall <zzqq0103.hey@gmail.com> wrote:
> Hello,
>
> I am writing to report a potential vulnerability identified in the
> Linux Kernel version 2.6.26.
> This issue was discovered using our custom vulnerability discovery
> tool.
>
> Affected File:
>
> File: net/sched/sch_dsmark.c
> Function: qdisc_create
>
> Detailed call trace:
You are testing a kernel that is no longer supported.
The 2.6.26 kernel was end-of-life in November 2008
The dsmark qdisc was removed a year ago in 6.3 kernel.
prev parent reply other threads:[~2024-12-02 5:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-02 4:31 "Bug in qdisc_create" in Linux kernel version 2.6.26 cheung wall
2024-12-02 5:27 ` Stephen Hemminger [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20241201212747.13b37633@hermes.local \
--to=stephen@networkplumber.org \
--cc=davem@davemloft.net \
--cc=hadi@cyberus.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=zzqq0103.hey@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox