linux-kernel - Re: [PATCH] tty: ipwireless: Fix use-after-free in tasklet during device removal

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <p16239r9-692o-859r-6006-7o611r2rn2qs@xreary.bet>
Date: Sun, 8 Feb 2026 18:25:38 +0100 (CET)
From: Jiri Kosina <jikos@...nel.org>
To: Greg KH <gregkh@...uxfoundation.org>
cc: duoming@....edu.cn, linux-serial@...r.kernel.org, 
    linux-kernel@...r.kernel.org, dsterba@...e.com, jirislaby@...nel.org, 
    kuba@...nel.org, alexander.deucher@....com, akpm@...ux-foundation.org, 
    pkshih@...ltek.com, tglx@...nel.org, mingo@...nel.org
Subject: Re: [PATCH] tty: ipwireless: Fix use-after-free in tasklet during
 device removal

On Sun, 8 Feb 2026, Greg KH wrote:

> > I don't have the real hardware. In order to reproduce the bug, I simulate 
> > the IPWireless PCMCIA card in the qemu by allocating and configuring the 
> > necessary resources(I/O ports, memory regions, interrupts and so on) to
> > correspond with the hardware expected by the driver in the initialization 
> > code of the virtual device.
> 
> I wonder if this device even is still around, given that pcmcia is all
> but dead for a very long time.

I doubt that this device is still around anywhere where reasonably new 
kernels (including LTS) would matter.

I don't think I've seen this device (which was back then donated to me by 
T-Mobile CZ in order to get it supported in Linux, and I am not sure how 
much global adoption it got afterwards) for, let's say, past 15 years :)

I think (let's see what David, ho took the maintainership over for me 
afterwards, has to say) we'd better deprecate and drop the whole thing, 
rather than trying to pretend that it's still actively being taken care 
of.

-- 
Jiri Kosina
SUSE Labs