Netdev List
 help / color / mirror / Atom feed
From: co <co+4638111fe2a12980@bugs.sh>
To: netdev@vger.kernel.org,
	Subash Abhinov Kasiviswanathan
	<subash.a.kasiviswanathan@oss.qualcomm.com>,
	Sean Tranchetti <sean.tranchetti@oss.qualcomm.com>,
	Andrew Lunn <andrew+netdev@lunn.ch>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>
Cc: linux-kernel@vger.kernel.org, co <co+4638111fe2a12980@bugs.sh>
Subject: [BUG] drivers/net: NULL pointer dereference in rmnet_map_send_ack()
Date: Thu, 20 Aug 2026 01:02:59 -0700	[thread overview]
Message-ID: <ijg79FFMfIvKJbivdJEKvTO90Q9dTvyBkJck@bugs.sh> (raw)

We found a bug reachable in:

    path    drivers/net/ethernet/qualcomm/rmnet
    crash   NULL pointer dereference in rmnet_map_send_ack()
    commit  b027ca66ec02

Config, environment, the sanitizer report and a C reproducer follow.

== Notes ===============================================================
    If you patch the bug based on our artifacts, a tag would be
    appreciated:

Reported-by: co+4638111fe2a12980@bugs.sh

    Everything in this mail is validated by the reproducer below.

    We also hold an LLM-generated root-cause analysis and a candidate
    patch. The patch passes an A/B test: the same reproducer panics the
    unpatched kernel and runs clean on the patched one. Neither has had
    human review, so both still require validation before you send or
    apply them. Available on:

        patch.diff  https://bugs.sh/b/4638111fe2a12980/patch.diff
        report.md   https://bugs.sh/b/4638111fe2a12980/report.md

    This is an open science project. The code and the full set of PoCs
    are not public at this moment, as we intend to disclose our findings
    in an ethical way.

    Happy to test patches. Complaints and suggestions about our work
    are welcome at:

        cedalion@bugs.sh

== Environment =========================================================
    Reproduced on  b027ca66ec02
    VM setup       https://bugs.sh/b/4638111fe2a12980/run.sh
    config         https://bugs.sh/b/4638111fe2a12980/config.gz
    poc            https://bugs.sh/b/4638111fe2a12980/repro.c

== Sanitizer Report ====================================================
Oops: general protection fault, probably for non-canonical address 0xdffffc00000000b2: 0000 [#1] SMP KASAN NOPTI
KASAN: null-ptr-deref in range [0x0000000000000590-0x0000000000000597]
CPU: 0 UID: 0 PID: 5011 Comm: exploit Not tainted 7.2.0-rc7-00095-g24ef02f934ee #33 PREEMPT(full)
RIP: 0010:kasan_byte_accessible+0x15/0x30
Call Trace:
__kasan_check_byte+0x13/0x50
lock_acquire+0x136/0x360
_raw_spin_lock+0x2e/0x40
netif_tx_lock+0x19/0x30
rmnet_map_command+0x213/0x320
__rmnet_map_ingress_handler+0x57a/0x900
rmnet_rx_handler+0x350/0x4d0
__netif_receive_skb_core.constprop.0+0x6bf/0x3610
__netif_receive_skb_one_core+0xb0/0x1e0
__netif_receive_skb+0x1f/0x120
netif_receive_skb+0x13e/0x7d0
tun_rx_batched.isra.0+0x3ee/0x740
tun_get_user+0x2874/0x3aa0
tun_chr_write_iter+0xdc/0x210
vfs_write+0x6ac/0x1050
ksys_write+0x12a/0x250
do_syscall_64+0x116/0x7d0
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x4240c4
RIP: 0010:kasan_byte_accessible+0x15/0x30
Kernel panic - not syncing: Fatal exception in interrupt
Kernel Offset: disabled
Kernel panic - not syncing: Fatal exception in interrupt


---
The report format is based on syzbot bug report.

This report is generated by a bot. It may contain errors.
See https://github.com/n132/cedalion for more information.

For any issue with this report, reach out to cedalion@bugs.sh

If the report is already addressed, let us know by replying with:
#co fix: <commit hash>

If the report is a duplicate of another one, reply with:
#co dup: <lore link>

If you want to undo deduplication, reply with:
#co undup


                 reply	other threads:[~2026-08-20  8:03 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=ijg79FFMfIvKJbivdJEKvTO90Q9dTvyBkJck@bugs.sh \
    --to=co+4638111fe2a12980@bugs.sh \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=sean.tranchetti@oss.qualcomm.com \
    --cc=subash.a.kasiviswanathan@oss.qualcomm.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