CIP-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@nabladev.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Nobuhiro Iwamatsu <nobuhiro.iwamatsu.x90@mail.toshiba>,
	Pavel Machek <pavel@nabladev.com>, Ulrich Hecht <uli@fpond.eu>,
	Masami Ichikawa <masami.ichikawa@miraclelinux.com>,
	cip-dev <cip-dev@lists.cip-project.org>
Subject: Re: CVE-2026-64560
Date: Thu, 30 Jul 2026 23:09:13 +0200	[thread overview]
Message-ID: <amu9ef9UvmeIKKWN@duo.ucw.cz> (raw)
In-Reply-To: <4d61ec83-bb55-4c27-b370-0e2ed60bd800@siemens.com>

[-- Attachment #1: Type: text/plain, Size: 651 bytes --]

Hi!

> this looks like it does not need special drivers and is not that easy
> to mitigate (CONFIG_POSIX_TIMERS=n...):
> 
> https://git.kernel.org/pub/scm/linux/security/vulns.git/commit/?id=081d2ff9592751aa400828237f17c108e4e1f513
> 
> Early releases?

No cool name, no logo, and no website? Aint doing no release for that!

So... this is crasher, and you need local access for it. In my eyes,
it is below "Dirty Cow" in severity.

https://lwn.net/Articles/1086226/

But this is 6.12.100. Something tells me 6.12.99 and .98 are fixing
similar issues. So... I guess we should investigate some more.

Best regards,
								Pavel


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

  reply	other threads:[~2026-07-30 21:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-30 20:33 CVE-2026-64560 Jan Kiszka
2026-07-30 21:09 ` Pavel Machek [this message]
     [not found] ` <18C72D766E036C67.1779571@lists.cip-project.org>
2026-07-30 21:44   ` [cip-dev] CVE-2026-64560 Pavel Machek
2026-07-31  5:12     ` Jan Kiszka

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=amu9ef9UvmeIKKWN@duo.ucw.cz \
    --to=pavel@nabladev.com \
    --cc=cip-dev@lists.cip-project.org \
    --cc=jan.kiszka@siemens.com \
    --cc=masami.ichikawa@miraclelinux.com \
    --cc=nobuhiro.iwamatsu.x90@mail.toshiba \
    --cc=uli@fpond.eu \
    /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