Subcategories

  • 2 Topics
    2 Posts
    peat_psuwitP
    Vulnerability During the periodic scanning of the local media, gst-hybris gets loaded by Gstreamer, a media framework, to perform HW-accelerated video decoding. gst-hybris expected the rendering element ("sink") to be HW-accelerated as well, but media scanning does not use HW-accelerated rendering. This results in memory corruption, which could potentially be exploited by a specifically-crafted media. Info The pipeline constructing process of Gstreamer is dynamic; it can automatically pick the demuxer, decoder(s), and sink(s) based on the file type, file content, and component's capability. In this case, Gstreamer picks gst-hybris' HW-accelerated decoder as the decoder, but "fakesink" as the sink (as the scanner only wants to know certain metadata). Now, to perform HW-accelerated video rendering, gst-hybris has a dedicated sink which co-operate with the decoder in order to pass decoded video frame without copying the memory. When Gstreamer connects the decoder with the sink, the decoder can access the sink to perform necessary co-ordination. However, the decoder forgot to check if the sink it accesses is the one it can co-operate, which results in the code writing into the memory it's not supposed to access. In order for this to be exploited, the video has to be on the device, which subsequently leads to it being scanned. Video playback in other cases is not affected, as they always use HW-accelerated video rendering. CWE-843: Access of Resource Using Incompatible Type ('Type Confusion') Severity: Medium Affected versions Affected versions: All Ubuntu Touch versions up to and including 20.04 OTA-10, 24.04-1.0. Fixed in versions: Ubuntu Touch 20.04 OTA-11 and 24.04-1.1. Solution Starting in Ubuntu Touch 20.04 OTA-11 and 24.04-1.1, gst-hybris checks the type of the sink before casting to the expected type. Fixed in: https://gitlab.com/ubports/development/core/hybris-support/gst-hybris/-/commit/58bb0e1ba2169bd85ac0930bf074ab865553356f Recommendations Update your device to Ubuntu Touch 20.04 OTA-11, 24.04-1.1 or newer. Do not download videos from untrusted sources. Timeline The issue was discovered on 30 September 2025, during a debugging of another issue. The issue was discovered before the release of Ubuntu Touch 24.04-1.0, but we did not manage to work it through and fix it in time for that release. Ubuntu Touch 20.04 OTA-11 and 24.04-1.1 was released on 1 December 2025, coordinated with the publication of this advisory. Credit Reported-by: Ratchanan Srirattanamet Patched-by: Ratchanan Sirrattanamet
  • This forum is all about the ongoing efforts to upgrade UT to the 20.04 codebase of Ubuntu.

    132 Topics
    954 Posts
    A
    @Moem @Luksus This is good news as this was a good phone with UBPorts
  • Add Avahi daemon

    3
    1 Votes
    3 Posts
    889 Views
    N
    On a WiFi network you usually want as little Multicast/Broadcast traffic as possible so I suggest that IF you add Avahi then please make sure it's DISABLED by DEFAULT On all my other Linux devices it's also Disabled where it can be and if it can be!
  • how different is UT when compared to a computes os

    8
    0 Votes
    8 Posts
    2k Views
    MoemM
    @somannak said in how different is UT when compared to a computes os: That answers most of my questions for now. Niiice!
  • High CPU usage by kworker

    20
    5
    0 Votes
    20 Posts
    5k Views
    K
    I'm on RC (starting with 113, now 115) with my E4.5 for over 10 days now and I haven't been affected by this bug anymore.
  • This topic is deleted!

    1
    0 Votes
    1 Posts
    34 Views
    No one has replied
  • Password and lock code

    2
    0 Votes
    2 Posts
    419 Views
    K
    Currently, no.
  • Ubuntu touch version - where is the changelog?

    9
    1 Votes
    9 Posts
    2k Views
    dobeyD
    @unisuperbox There is the "merge events" filter on https://gitlab.com/groups/ubports/-/activity though. Granted it's not exact for what one might have gotten on their device, and you can't limit it to last 24 hours. But its's as reasonable a rough overview of changes as the aforementioned GitHub search query, I think.
  • Wireguard VPN support?

    2
    0 Votes
    2 Posts
    993 Views
    dobeyD
    AFAIK, nobody is working on support for Wireguard currently. Most device kernels also don't have support for it. I guess there is a way to do it only in user space, but I am not sure what all the requirements are. If you want to open feature requests about what needs to be done to support it, and perhaps provide some pull requests for them, I'm sure it would be greatly appreciated.
  • What's the dev team's workflow for editing core apps?

    Unsolved
    3
    0 Votes
    3 Posts
    714 Views
    K
    @keneda That's the intent - but would hate to get a community's hopes up until this thing works for one person. As for the tweak's contents, it's issue #727 on GitHub. I don't like that it's still open.
  • Driverless wifi printing

    18
    1 Votes
    18 Posts
    3k Views
    A
    Over in the Sailfish universe we have SeaPrint (by me)... so if someone wants to port it, feel free to get in touch. No CUPS dependencies, strictly speaking no dependencies at all other than Qt, but poppler is needed for working with simpler printers.
  • Ubuntu Touch OTA-18 Changelog: qtubuntu-camera

    5
    0 Votes
    5 Posts
    1k Views
    U
    Hi, ma! Thanks for your interest! qtubuntu-camera is a piece of software that allows Qt applications to use cameras on Android devices through hybris. Adding these new values means that Qt applications can use them. It does not mean that they will start using them automatically. There needs to be a change done to the camera-app software, which uses qtubuntu-camera, to support the new flash and exposure modes. There is a Merge Request filed to enable more flash modes: https://gitlab.com/ubports/apps/camera-app/-/merge_requests/154. However, there is no merge request filed to enable more exposure modes. If you like, you can help us test and create these changes as needed.
  • Ubuntu Touch OTA-18 Changelog

    Locked
    2
    11 Votes
    2 Posts
    2k Views
    T
    @unisuperbox Thank you for a change log.
  • OTA-18 Call for Testing Companion Post

    Moved
    1
    2 Votes
    1 Posts
    675 Views
    No one has replied
  • The MMS lost story

    Locked
    133
    4 Votes
    133 Posts
    87k Views
    LakotaubpL
    As @jezek and @lduboeuf suggested this thread is very long and far to hard to follow. So I will lock it. A fix has been posted so please as asked try it and report issues in the normal way and let's see how it goes.
  • Where does UT store volume levels?

    6
    0 Votes
    6 Posts
    1k Views
    dobeyD
    @trwidick I wouldn't guess alsa, as for pulseaudio we have a droid plug-in whiich talks to HAL on Android devices.
  • 2 Votes
    5 Posts
    1k Views
    A
    Interesting. I had heard about it, but never really read about it.
  • PICTURE MESSAGES SENT SIDEWAYS

    12
    0 Votes
    12 Posts
    1k Views
    T
    Bug report opened on GitHub. https://github.com/ubports/ubuntu-touch/issues/1751
  • This topic is deleted!

    1
    0 Votes
    1 Posts
    1 Views
    No one has replied
  • A new way for desktop applications(classical application)

    9
    0 Votes
    9 Posts
    2k Views
    T
    @thomas-k8s Nah, you lose the native XMir windowing with that. I'm more partial to how we did it in the days before libertine's release back in 15.04 (still chroot, not libertine's proot which seems more restrictive, but using XMir with matchbox-window-manager to provide some semblance of window managment) Nowadays, I'm looking into something similar, but using the Gentoo Prefix in place of the chroot, so it runs unprivileged. Obviously will generate a LOT of I/O so if anyone else goes this way, I highly recommend running the bootstrap as far as it will let you using an NFS root mounted into the home directory somewhere (mine is .local/system) and then copy it to device and finish the bootstrap using an NFS-mounted TMPDIR (because bootstrap will only let you go so far before portage tells you that it needs root permissions for some reason when bootstrapping straight to an NFS shared folder)
  • Qemu-kvm or QEMU on ubuntu touch?

    10
    0 Votes
    10 Posts
    4k Views
    T
    @emphrath No problem, I've tried a lot of things that most people would find "useless" under ubPorts while working to make my trusty Nexus 7 a portable workstation. I've been tempted to add WINE to my setup again, but I don't want to deal with setting up an i386 chroot running on the device (since LXC doesn't function correctly for me, can't create LXC containers, oddly the Android container works fine). In case I didn't mention it previously, yes, it requires qemu-user-static installed and you have to have an i386 chroot to install and run WINE/32.
  • Running docker on ubuntu touch?

    5
    0 Votes
    5 Posts
    5k Views
    T
    @saveurlinux It did not work