/srv/irclogs.ubuntu.com/2022/03/10/#ubuntu-security.txt

SvenKieskehi there, I was referred here from the "ubuntu-kernel" channel. I just wanted to ask if "linux-generic-hwe-20.04-edge" will get the update for "linux-generic-hwe-20.04-edge"? the metapackage seems not to be updated (yet)?09:20
SvenKieskesorry, c&p error, I meant if the hwe-edge kernel will get the update for https://ubuntu.com/security/CVE-2022-084709:21
ubottuA flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe and push_pipe functions in the Linux kernel and could thus contain stale values. An unprivileged local user could use this flaw to write to pages in the page cache backed by read only files and as such escalate their privileges on the syste... <https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-0847>09:21
SvenKieskeah, and if you don't mind, what does "Does not exist" even mean, on these CVE pages? I really couldn't figure that one out. All help would be highly appreciated, thanks in advance :)09:22
amurrayDoes Not Exist means that a given packaged is not published in a particular Ubuntu release - so as you can see this kernel is superceded by the linux-hwe kernel so you should use that one instead as linux-hwe-edge will not be updated for this or other CVEs09:29
amurrays/packaged/package/09:29
amurrayah I see I was looking at the wrong package name - linux-generic-hwe-20.04-edge comes from the linux-meta-hwe-5.13 source package - and this has already been patched (see linux-hwe-5.13 on the CVE page)09:34
amurraytracking which kernel package is built from which source is a bit of a fine art09:34
SvenKieskeyeah09:35
SvenKieskebut I was just informed in #ubuntu-kernel, that "hwe-edge" in general receives no security updates at all, which is good to know, too..09:35
SvenKieskeI still find it weird, that the patch seems to be in git (but maybe I'm looking at the wrong git): https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/focal/commit/?h=hwe-5.13&id=438da6e5c849ffe553fc15379471bf331346c3d209:36
ubottuCommit 438da6e in ~ubuntu-kernel/ubuntu/+source/linux/+git/focal "UBUNTU: Ubuntu-hwe-5.13-5.13.0-35.40~20.04.1 Ubuntu-hwe-5.13-5.13.0-35.40_20.04.1 hwe-5.13"09:36
SvenKieskenvm, that's "hwe", not "hwe-edge"...args..ubuntu has too many kernel variants.. (for my peculiar usecase). anyway, thanks!09:37
JanCmaybe the -edge kernel shouldn't be in 'main' if it is not officially supported...09:39
LocutusOfBorgmdeslaur 16:40
LocutusOfBorgThe specific flaw exists in bionic and focal, but is not16:40
LocutusOfBorgcurrently exploitable due to lack of a flag that was introduced16:40
LocutusOfBorgin kernel 5.8. The flaw will be fixed as part of the next round16:40
LocutusOfBorgof bionic and focal kernel updates in case some other way of16:40
LocutusOfBorgexploiting it is discovered in the future.16:40
LocutusOfBorgmdeslaur, ^^16:40
LocutusOfBorgspeaking of CVE-2022-084716:41
ubottuA flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe and push_pipe functions in the Linux kernel and could thus contain stale values. An unprivileged local user could use this flaw to write to pages in the page cache backed by read only files and as such escalate their privileges on the syste... <https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-0847>16:41
LocutusOfBorgI checked on focal16:41
LocutusOfBorgand I exploited my own machine...16:41
LocutusOfBorgnevermind16:41
LocutusOfBorgLinux Unimatrix08-Focal 5.13.0-30-generic #33~20.04.1-Ubuntu SMP Mon Feb 7 14:25:10 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux16:41
LocutusOfBorg:)16:41
mdeslauryeah, that's the HWE kernel, and that one got an update17:30
mdeslaurI'll clarify in my note17:30
LocutusOfBorgactually was my fault17:49
LocutusOfBorgI forgot about hwe kernel17:49
mdeslaursomeone else asked me the same thing, so clarifying the note is worth it17:55
LocutusOfBorgoh ok :D18:01
ricotzmdeslaur, hi, fyi https://git.launchpad.net/~libreoffice/ubuntu/+source/libreoffice/commit/?h=ubuntu-impish-7.2&id=c17b727d4ec5bc20678122303ca118ea8f7c5e3d20:51
ubottuCommit c17b727 in ~libreoffice/ubuntu/+source/libreoffice "Restrict parallelism to 3 on amd64"20:51
ricotzafaict lgw01 builders were capable, but lcy02 are not :(20:52
ricotzmdeslaur, also https://launchpad.net/ubuntu/+source/libreoffice/1:7.2.6-0ubuntu0.21.10.120:53
mdeslaurricotz: oh! that's why that was failing...thanks for the hint!20:54
mdeslaurricotz: I saw the new version in -proposed, so I'll rebuild mine based on it20:54
ricotzmdeslaur, is there really another rebuild for impish needed?20:55
mdeslaurricotz: it needs to go into the -security pocket so it gets installed with unattended-upgrades20:55
mdeslaurricotz: to go in the -security pocket, it needs to be built with -updates disabled20:56
ricotzmdeslaur, so using the currently running build is not an option?20:56
ricotzI see20:56
mdeslaurricotz: the -security vs -updates split is annoying20:56
ricotzmdeslaur, better just pick the build fix for 7.2.5 then?20:56
ricotzstill why the rebuild needed?20:57
ricotzexpat isn't statically linked20:57
mdeslaurbecause if it builds against -updates, it may get dependencies that exist only in -updates20:58
mdeslaurwhich would render it uninstallable when only -security is enabled20:58
ricotzok, please use 7.2.5 then20:59
mdeslaurwhy 7.2.5 instead of 7.2.6?21:00
ricotzto respect the SRU process?21:00
mdeslaurI'll wait a week for 7.2.6 to get released21:00
mdeslaurI'm in no hurry for the security updates, it can wait21:00
ricotzalright21:02
ricotzmdeslaur, please feel free to ping in such occasions21:03
mdeslaurricotz: if might be simpler to have the SRUs be built without -updates enabled in the future, so they can simply be copied to -security21:04
mdeslaurwe can discuss it next time there's an update to do, either an SRU or a security update21:04
ricotzack, as long there is nothing vital in -updates/-proposed21:06
ricotze.g. glib/gtk3/qt5 updates can be runtime deps21:07
mdeslauryeah, if there is, I have to rebuild them in -security21:08
mdeslaurhappens once in a while21:08
ricotzthis won't help if the tests or autopkgtests are failing21:09
mdeslaurwhat do you mean?21:09
ricotzI mean if a library dependency is fixing runtime issues which are affecting the results of tests/autopkgtests you would need those newer versions21:11
mdeslauryes, and in which case I would rebuild then as no-change rebuilds in the -security pocket21:11
ricotzbut the package would fail to build21:12
mdeslaurif libreoffice needs the newer glib from -updates to pass the autopkgtests, I need to first build glib in -security, release it, then I can build libreoffice in -security21:13
mdeslaurwhat would fail to build?21:13
ricotzalright21:13
ricotz"make check" is fatal on amd64/arm6421:13
ricotzI don't remember seeing this in the past, but I usually build/test with -updates/-proposed21:15
mdeslauryeah, as I've said, I really hate the -security/-updates split, but around 30% of our customers run with -updates disabled, and for the rest, unattended-upgrades won't pull stuff from -updates21:16
mdeslaurso the only way for users to get security updates is to have stuff in the -security pocket, built with -updates disabled21:17
mdeslaurand when that doesn't happen, we get pinged21:18
ricotzI understand, just indicating possible ill effects21:18
* mdeslaur nods21:19

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!