This bug was fixed in the package apparmor - 4.1.0~beta5-0ubuntu14.1
---------------
apparmor (4.1.0~beta5-0ubuntu14.1) plucky; urgency=medium
* This is an SRU from Questing to Plucky, tracked in LP: #2110236
* Add patch to allow unprivileged_userns access to root dir
(LP: #2110616):
- d/p/u/unprivileged_userns_rootdir.patch
* Add patch to fix lsblk accesses on IBM System Z systems (LP: #2107402)
and execution from a confined context (LP: #2107455):
- d/p/u/lsblk-s390-fixes.patch
* Add patch to fix execution of various commands from confined contexts
(LP: #2110628):
- d/p/u/profiles_ensure_access_to_attach_path.patch
* Add patch to include new QtWebEngineProcess execution path in
plasmashell profile (LP: #2107723):
- d/p/u/plasmashell-QtWebEngineProcess-new-path.patch
* Add patch to allow /cvmfs fusermounts (LP: #2110624):
- d/p/u/fusermount3_cvmfs.patch
* Add patch to grant OpenVPN DNS accesses (LP: #2107596, LP: #2109029):
- d/p/u/openvpn_dnsfix.patch
* Add patch to expand allowed fusermount3 flags for fuse_overlayfs and
sshfs via fstab (LP: #2110626, LP: #2111807):
- d/p/u/fusermount3_allow_more_flags.patch
* Add patch to fix permission denials for iotop-c (LP: #2107727):
- d/p/u/profiles-give-iotop-c-additional-accesses.patch
* Add patch to fix parser handling of norelatime mount flag
(LP: #2110688):
- d/p/u/parser-fix-handling-of-norelatime-mount-rule-flag.patch
* Add patch to fix incorrect mount rule documentation in the apparmor.d
man page (LP: #2110630):
- d/p/u/fix-incorrect-mount-flag-apparmor.d-docs.patch
* Add patch to add regression tests for the above two patches:
- d/p/u/regression-verify-documented-mount-flag-behavior.patch
* d/p/u/remmina_mr_1348.patch, d/p/u/remmina-dbus-describeall.patch:
move the remmina profile to profiles/apparmor/profiles/extras to
disable it by default (LP: #2102033)
* debian/apparmor.install: remove the remmina profile entry
* debian/apparmor-profiles.install: add an entry for the remmina profile
* debian/apparmor.maintscript: remove the remmina profile upon upgrade
-- Ryan Lee <[email protected]> Wed, 27 May 2025 11:29:02 -0700
** Changed in: apparmor (Ubuntu Plucky)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/2110616
Title:
apparmor unprivileged_userns profile missing access to /
Status in apparmor package in Ubuntu:
Fix Released
Status in apparmor source package in Plucky:
Fix Released
Status in apparmor source package in Questing:
Fix Released
Bug description:
[ Impact ]
The unprivileged_userns profile did not grant access to the root
directory, which was an oversight in a profile that is intended to
allow almost all accesses except for capabilities usage. This would
e.g. break listing of the root directory contents from a user
namespace.
[ Test Plan ]
After installation of the new AppArmor version:
* Ensure that the sysctl kernel.apparmor_restrict_unprivileged_unconfined is
set to 1
* Run `sudo aa-status` and verify that an unprivileged_userns profile is
loaded
* Run unshare -U ls / and verify that it lists the directory successfully
without creating an AppArmor denial log
[ Where problems could occur ]
Changing the rule to allow access to the root directory is loosening
confinement on the profile. However, if a user manually modified the
installed profiles, then the package upgrade would cause conflicts,
and rejection of the incoming changes (either by hand during an
interactive upgrade or automatically during an batch unattended
upgrade) would result in end users not getting this fix.
[ Other Info ]
This bug was originally reported at
https://gitlab.com/apparmor/apparmor/-/issues/505.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2110616/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
