Mandriva Update for sound-scripts MDVA-2008:168 (sound-scripts)

Published: 2009-04-09 12:09:08

CVSS Base Vector:

Check for the Version of sound-scripts

Affected Versions:
sound-scripts on Mandriva Linux 2009.0, Mandriva Linux 2009.0/X86_64

Please Install the Updated Packages.

Technical Details:
The sound initialization scripts provided with Mandriva Linux 2009 activate the Analog Loopback channel when it is present. This channel is present on most audio chipsets supported by the snd-hda-intel driver, which are commonly used on recent systems. When active, this channel plays back the sound received by the line-in and mic-in channels. If nothing is actually connected to these channels, this can result in an unpleasant loud noise over the speakers or headphones connected to the line-out or speaker-out connector. This update adjusts the sound initialization scripts to mute this channel by default. Unfortunately, this change will not be applied automatically on already-installed systems, as existing settings are automatically stored at shutdown and re-applied at startup on Mandriva Linux. If you are suffering from this issue, then you can run the command 'reset_sound' as root after installing this update, and it should resolve the issue. Alternatively, you can simply disable / mute the Analog Loopback channel yourself, using a mixer application.

Detection Type:
Linux Distribution Package

Solution Type:
Vendor Patch


CVSS Score
Mandrake Local Security Checks

Free Vulnerability Scanning, Assessment and Management

Mageni's Platform is packed with all the features you need to scan, assess and manage vulnerabilities like this - it is free, open source, lightning fast, reliable and scalable.


Frequently Asked Questions

No, you can scan concurrently as many assets as you want. Please note that you must be aware of the hardware requeriments of the platform to ensure a good performance.

No, you can add as many assest as you want. It doesn't matters if you have millions of assets, we won't charge you for that.

No. The software is completely free. We have no intention to charge you to use the software, in fact - it completely goes against our beliefs and business model.

A vulnerability is defined in the ISO 27002 standard as “A weakness of an asset or group of assets that can be exploited by one or more threats” (International Organization for Standardization, 2005)

We generate revenue by providing support and other services for customers that require a subscription so they get guaranteed support and enterprise services. To use Mageni's Platform is completely free, with no limits at all.

Yes. Mageni understands that there are professionals and businesses that need commercial support so Mageni provides an active support subscription with everything needed to run Mageni's Platform reliably and securely. More than software, it's access to security experts, knowledge resources, security updates, and support tools you can't get anywhere else. The subscription includes:

  • Ongoing delivery
    • Patches
    • Bug fixes
    • Updates
    • Upgrades
  • Technical support
    • 24/7 availability
    • Unlimited Incidents
    • Specialty-based routing
    • Multi-Channel
  • Commitments
    • Software certifications
    • Software assurance
    • SLA

No, we don't store the information of your vulnerabilities in our servers.

Vulnerability management is the process in which vulnerabilities in IT are identified and the risks of these vulnerabilities are evaluated. This evaluation leads to correcting the vulnerabilities and removing the risk or a formal risk acceptance by the management of an organization. The term vulnerability management is often confused with vulnerability scanning. Despite the fact both are related, there is an important difference between the two. Vulnerability scanning consists of using a computer program to identify vulnerabilities in networks, computer infrastructure or applications. Vulnerability management is the process surrounding vulnerability scanning, also taking into account other aspects such as risk acceptance, remediation etc. Source: "Implementing a Vulnerability Management Process". SANS Institute.

I am ready to start scanning for vulnerabilities