Re: [PATCH net 0/2] net: phy: fix timestamping lifetime after probe failure

From: Kimberly Morris

Date: Wed Nov 18 2026 - 05:57:46 EST


> - How the issue was discovered, e.g. hit in production, hit during
> development, syzbot report, manual code inspection, LLM or static
> analysis tool scan.

The issue was found during a targeted source audit of PHY hardware
timestamping lifetime and probe-error paths. The source audit was assisted
by an LLM; it was not a production report or a syzbot finding.

The resulting hypothesis was then validated against the current Linux
source with a focused KUnit/KASAN reproducer. The test registers a real
mii_bus, phy_device and phy_driver, follows phylib's probe failure and the
driver core's devres cleanup, attaches the generic PHY driver, and calls
skb_defer_rx_timestamp() with a non-PTP skb. KASAN reported the
use-after-free before the fix, and the same test passed after the fix.

The concrete BCM54210E/BCM54213PE publication-before-failure ordering and
the missing PHC cleanup were also checked directly in the driver source.
No physical hardware reproduction has been completed.

On Wed, 18 Nov 2026 10:38:42 +0000, netdev-bot+sinfo@xxxxxxxxxx wrote:
> Hi!
>
> This is an automated message. This series looks like a fix, but its
> commit messages seem to be missing some information:
>
> - How the issue was discovered, e.g. hit in production, hit during
> development, syzbot report, manual code inspection, LLM or static
> analysis tool scan.
>
> Please do not repost the series just to address the above. Instead,
> reply to this email with the missing information, so that reviewers
> can take it into account.
>
> *IMPORTANT*: If you do repost (for other reasons) - please include
> the relevant info in the cover letter or commit messages.
> --
> The evaluation is done by an LLM so it may be wrong, if you think
> that is the case please reply and explain.